I am messing around with a few computers at my place and I have them netwokred.
I want to deploy and update SAV Corp Client via SAV server, but it keeps telling me that such and such computer is not part of the local group ADMIN$...
Is there anyway of allow my server to access the system(s) that run WinXP Home?
My System that runs SAV server is WinXp PRO.
How do you set up a local admin group for XP Home... is it possible?
Trying to teach my self some networking and i have looked all over for this.
Thanks.
Full Version: Local admin group (ADMIN$)???
Anyone?
The only way I know of to add another computer to a local group is through Active Directory, which requires Server (2K or 2K3).
I have found out that there are no groups on XP Home so you are on your own. Just learned it stupor-bowel sunday in fact. I tried to have someone modify a local security policy for XP Home and found out XP Home should NEVER be used except for old and decrepid people or minds.
XP Pro gives you abilites to network computers in a corporate setting. What you are trying to do is NOT a normal household thing.
Why not buy licsense only XP Pro licenses for 50 bucks each and re-register the Home boxes? Then you can do more stuff.....
XP Pro gives you abilites to network computers in a corporate setting. What you are trying to do is NOT a normal household thing.
Why not buy licsense only XP Pro licenses for 50 bucks each and re-register the Home boxes? Then you can do more stuff.....
QUOTE(AceHigh @ Feb 2 2004, 05:51 PM)
The only way I know of to add another computer to a local group is through Active Directory, which requires Server (2K or 2K3).
I think you are talking about GLOBAL groups Ace dude man....
I'm sure SAV requires a domain, now teach yourself Active Directory. 
I installed 3 NAV Corp's recently... all the clients were XPPro and 2000, also a 2K server with a domain was the NAV server....
Never used any Home's as they can't connect to the domain...
You want fun... get a Novell 4.12 server to update automatically...
Sorry Odie cant help...
Never used any Home's as they can't connect to the domain...
You want fun... get a Novell 4.12 server to update automatically...
Sorry Odie cant help...
QUOTE(Jason @ Feb 2 2004, 07:16 PM)
I'm sure SAV requires a domain, now teach yourself Active Directory.
means nothing to XP Home dude.....
Jason, I don't think you can put XP Home Edition on an Active Directory (i.e. Domain Controller). The networking is limited to Workgroups and not domains.
Here it is from the horses ass... er mouth
IPSec in Windows XP Home Edition
QUOTE
IPSec in Windows XP Home EditionBecause a computer running Windows XP Home Edition cannot be a member of an Active Directory domain and does not include support for the Kerberos V5 protocol, it has the following limitations:
It cannot receive domain-based IPSec policy and participate in an Active Directory managed security environment.
A computer running Windows XP Home Edition can only use IPSec policy that is configured on the local computer.
It cannot use the Kerberos V5 protocol to authenticate secure communications.
While this authentication option is available for selection in the IP Security Policies snap-in and is the authentication method selected for default IPSec policies, any attempt by a computer running Windows XP Home Edition to negotiate the Kerberos V5 protocol will result in a negotiation failure.
A computer running Windows XP Home Edition can use certificates and preshared key as authentication methods.
It cannot administer Active Directory-based IPSec policies with the IP Security Policies snap-in.
IPSec is included so that a computer running Windows XP Home Edition can:
Create remote access Layer Two Tunneling Protocol (L2TP) connections using IPSec to a Windows 2000 VPN server or any other VPN server that supports L2TP/IPSec. No customized or manual configuration of IPSec policy is required for L2TP/IPSec connections.
Secure specific types of traffic, provide port filtering, or make IPSec tunnel connections. This requires the custom configuration of local IPSec policy and is intended for network administrators and advanced users.
It cannot receive domain-based IPSec policy and participate in an Active Directory managed security environment.
A computer running Windows XP Home Edition can only use IPSec policy that is configured on the local computer.
It cannot use the Kerberos V5 protocol to authenticate secure communications.
While this authentication option is available for selection in the IP Security Policies snap-in and is the authentication method selected for default IPSec policies, any attempt by a computer running Windows XP Home Edition to negotiate the Kerberos V5 protocol will result in a negotiation failure.
A computer running Windows XP Home Edition can use certificates and preshared key as authentication methods.
It cannot administer Active Directory-based IPSec policies with the IP Security Policies snap-in.
IPSec is included so that a computer running Windows XP Home Edition can:
Create remote access Layer Two Tunneling Protocol (L2TP) connections using IPSec to a Windows 2000 VPN server or any other VPN server that supports L2TP/IPSec. No customized or manual configuration of IPSec policy is required for L2TP/IPSec connections.
Secure specific types of traffic, provide port filtering, or make IPSec tunnel connections. This requires the custom configuration of local IPSec policy and is intended for network administrators and advanced users.
That is Microsoft's words... not mine... so XP Home is for gramma and grampa grunt
you might be able to create a user profile in pro for xp and give it permissions in NTFS (inherit) then try to give it access to directory on the xp machine same way through NTFS security.Hope that made some sense 
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.