View Full Version : XP Home on a client/server network
I recently heard that the Home edition of XP won't work on
a client/server network. Is this true? If it's not I'd
like to save quite a bit of money by buying Home instead
of Professional.
Phil \(a.k.a. purplehaz\)
March 31st 04, 08:43 PM
Not true. XP pro or home can be networked just fine.
The only difference is that xp home cannot join a domain network. If you
have a workgroup network set up then xp home is fine. If you have to connect
to a domain network then you need xp pro.
Note: xp home can be tweaked so you can browse a domain network without
joining it.
wrote:
> I recently heard that the Home edition of XP won't work on
> a client/server network. Is this true? If it's not I'd
> like to save quite a bit of money by buying Home instead
> of Professional.
Phil \(a.k.a. purplehaz\)
March 31st 04, 08:44 PM
You're welcome.
wrote:
> Thanks Phil
Alex Nichol
April 1st 04, 08:02 PM
> wrote:
>I recently heard that the Home edition of XP won't work on
>a client/server network. Is this true? If it's not I'd
>like to save quite a bit of money by buying Home instead
>of Professional.
Home cannot 'join' a domain on a domain based net. It can work happily
on a work group one, and can log onto specific resources of a domain
with the administrator's permission, just like Win98 can. You have to
decide if that is adequate for your needs
--
Alex Nichol MS MVP (Windows Technologies)
Bournemouth, U.K. (remove the D8 bit)
>> Note: xp home can be tweaked so you can browse a domain network without
joining it.
Phil:
Home does not require any tweaking to use domain resources.
I use Home in a domain for the following:
NetBIOS networking
non-NetBT networking
Exchange server
ISA
Home cannot receive domain GPO, and Home cannot query AD.
>> Home cannot 'join' a domain on a domain based net. It can work happily
on a work group one, and can log onto specific resources of a domain
with the administrator's permission, just like Win98 can. You have to
decide if that is adequate for your needs
Alex:
Joining a domain means that the ws can have a computer acct in the domain
Active Directory (AD), and that the ws can receive Domain Admins gp and
Domain Users gp into the local ws SAM. Home cannot do either, so Home
cannot join a domain.
Note that generally, the computer acct is authenticated by a domain
controller (DC) during a user's local logon to a domain member computer when
that computer has connectivity with a DC. Since Home cannot have a domain
computer acct, it cannot be used for this type of authentication.
A user does not "log onto specific resources of a domain", a user is
authenticated by a domain controller (DC) to use domain resources, and that
authentication requires a domain user acct (a user always logs on "locally",
but he/she can be authenticated either locally or by a DC).
Generally, domain user acct authentication occurs when the user logs on to
his ws, and that ws has connectivity with a DC. Note that this is a
different authentication from the computer acct authentication mentioned
above.
A user on Home cannot be domain user acct authenticated by a DC during user
logon to Home.
However, when the user on Home attempts to use a domain resource, the domain
server for that resource can contact a DC for domain user acct
authentication. If the authentication is successful, then the normal domain
user controls apply (user rights, share perms, NTFS perms).
The phrase "with the administrator's permission" is misleading. Generally,
the domain administrator does not have to do anything different to setup a
domain user acct used by a Home user from what he/she would do for a user
logging in locally to a XP Pro ws that is a domain member.
I use Home in various domain setups, and it works great, provided a domain
user acct was used to logon locally to Home. What a domain user on Home
cannot do is receive domain GPO, and he/she cannot query AD.
A DC authenticated domain user logged onto Home can use the following domain
resources:
NetBIOS networking
non-NetBT networking
Exchange server
ISA
Brian Coats
April 6th 04, 07:26 PM
Hey cz? Inst their a 3 party application that will allow all this
with home?
>On Fri, 2 Apr 2004 07:53:31 -0800, "CZ" > wrote:
>>> Home cannot 'join' a domain on a domain based net. It can work happily
>on a work group one, and can log onto specific resources of a domain
>with the administrator's permission, just like Win98 can. You have to
>decide if that is adequate for your needs
>
>Alex:
>
>Joining a domain means that the ws can have a computer acct in the domain
>Active Directory (AD), and that the ws can receive Domain Admins gp and
>Domain Users gp into the local ws SAM. Home cannot do either, so Home
>cannot join a domain.
>Note that generally, the computer acct is authenticated by a domain
>controller (DC) during a user's local logon to a domain member computer when
>that computer has connectivity with a DC. Since Home cannot have a domain
>computer acct, it cannot be used for this type of authentication.
>
>A user does not "log onto specific resources of a domain", a user is
>authenticated by a domain controller (DC) to use domain resources, and that
>authentication requires a domain user acct (a user always logs on "locally",
>but he/she can be authenticated either locally or by a DC).
>Generally, domain user acct authentication occurs when the user logs on to
>his ws, and that ws has connectivity with a DC. Note that this is a
>different authentication from the computer acct authentication mentioned
>above.
>A user on Home cannot be domain user acct authenticated by a DC during user
>logon to Home.
>However, when the user on Home attempts to use a domain resource, the domain
>server for that resource can contact a DC for domain user acct
>authentication. If the authentication is successful, then the normal domain
>user controls apply (user rights, share perms, NTFS perms).
>
>The phrase "with the administrator's permission" is misleading. Generally,
>the domain administrator does not have to do anything different to setup a
>domain user acct used by a Home user from what he/she would do for a user
>logging in locally to a XP Pro ws that is a domain member.
>
>I use Home in various domain setups, and it works great, provided a domain
>user acct was used to logon locally to Home. What a domain user on Home
>cannot do is receive domain GPO, and he/she cannot query AD.
>
>A DC authenticated domain user logged onto Home can use the following domain
>resources:
>NetBIOS networking
>non-NetBT networking
>Exchange server
>ISA
>
>
>
Brian Coats
April 6th 04, 09:57 PM
Hey cz? Inst their a 3 party application that will allow all this
with home?
>On Fri, 2 Apr 2004 07:53:31 -0800, "CZ" > wrote:
>>> Home cannot 'join' a domain on a domain based net. It can work happily
>on a work group one, and can log onto specific resources of a domain
>with the administrator's permission, just like Win98 can. You have to
>decide if that is adequate for your needs
>
>Alex:
>
>Joining a domain means that the ws can have a computer acct in the domain
>Active Directory (AD), and that the ws can receive Domain Admins gp and
>Domain Users gp into the local ws SAM. Home cannot do either, so Home
>cannot join a domain.
>Note that generally, the computer acct is authenticated by a domain
>controller (DC) during a user's local logon to a domain member computer when
>that computer has connectivity with a DC. Since Home cannot have a domain
>computer acct, it cannot be used for this type of authentication.
>
>A user does not "log onto specific resources of a domain", a user is
>authenticated by a domain controller (DC) to use domain resources, and that
>authentication requires a domain user acct (a user always logs on "locally",
>but he/she can be authenticated either locally or by a DC).
>Generally, domain user acct authentication occurs when the user logs on to
>his ws, and that ws has connectivity with a DC. Note that this is a
>different authentication from the computer acct authentication mentioned
>above.
>A user on Home cannot be domain user acct authenticated by a DC during user
>logon to Home.
>However, when the user on Home attempts to use a domain resource, the domain
>server for that resource can contact a DC for domain user acct
>authentication. If the authentication is successful, then the normal domain
>user controls apply (user rights, share perms, NTFS perms).
>
>The phrase "with the administrator's permission" is misleading. Generally,
>the domain administrator does not have to do anything different to setup a
>domain user acct used by a Home user from what he/she would do for a user
>logging in locally to a XP Pro ws that is a domain member.
>
>I use Home in various domain setups, and it works great, provided a domain
>user acct was used to logon locally to Home. What a domain user on Home
>cannot do is receive domain GPO, and he/she cannot query AD.
>
>A DC authenticated domain user logged onto Home can use the following domain
>resources:
>NetBIOS networking
>non-NetBT networking
>Exchange server
>ISA
>
>
>
Brian Coats
April 7th 04, 05:51 AM
Hey cz? Inst their a 3 party application that will allow all this
with home?
>On Fri, 2 Apr 2004 07:53:31 -0800, "CZ" > wrote:
>>> Home cannot 'join' a domain on a domain based net. It can work happily
>on a work group one, and can log onto specific resources of a domain
>with the administrator's permission, just like Win98 can. You have to
>decide if that is adequate for your needs
>
>Alex:
>
>Joining a domain means that the ws can have a computer acct in the domain
>Active Directory (AD), and that the ws can receive Domain Admins gp and
>Domain Users gp into the local ws SAM. Home cannot do either, so Home
>cannot join a domain.
>Note that generally, the computer acct is authenticated by a domain
>controller (DC) during a user's local logon to a domain member computer when
>that computer has connectivity with a DC. Since Home cannot have a domain
>computer acct, it cannot be used for this type of authentication.
>
>A user does not "log onto specific resources of a domain", a user is
>authenticated by a domain controller (DC) to use domain resources, and that
>authentication requires a domain user acct (a user always logs on "locally",
>but he/she can be authenticated either locally or by a DC).
>Generally, domain user acct authentication occurs when the user logs on to
>his ws, and that ws has connectivity with a DC. Note that this is a
>different authentication from the computer acct authentication mentioned
>above.
>A user on Home cannot be domain user acct authenticated by a DC during user
>logon to Home.
>However, when the user on Home attempts to use a domain resource, the domain
>server for that resource can contact a DC for domain user acct
>authentication. If the authentication is successful, then the normal domain
>user controls apply (user rights, share perms, NTFS perms).
>
>The phrase "with the administrator's permission" is misleading. Generally,
>the domain administrator does not have to do anything different to setup a
>domain user acct used by a Home user from what he/she would do for a user
>logging in locally to a XP Pro ws that is a domain member.
>
>I use Home in various domain setups, and it works great, provided a domain
>user acct was used to logon locally to Home. What a domain user on Home
>cannot do is receive domain GPO, and he/she cannot query AD.
>
>A DC authenticated domain user logged onto Home can use the following domain
>resources:
>NetBIOS networking
>non-NetBT networking
>Exchange server
>ISA
>
>
>
Brian Coats
April 7th 04, 09:23 AM
Hey cz? Inst their a 3 party application that will allow all this
with home?
>On Fri, 2 Apr 2004 07:53:31 -0800, "CZ" > wrote:
>>> Home cannot 'join' a domain on a domain based net. It can work happily
>on a work group one, and can log onto specific resources of a domain
>with the administrator's permission, just like Win98 can. You have to
>decide if that is adequate for your needs
>
>Alex:
>
>Joining a domain means that the ws can have a computer acct in the domain
>Active Directory (AD), and that the ws can receive Domain Admins gp and
>Domain Users gp into the local ws SAM. Home cannot do either, so Home
>cannot join a domain.
>Note that generally, the computer acct is authenticated by a domain
>controller (DC) during a user's local logon to a domain member computer when
>that computer has connectivity with a DC. Since Home cannot have a domain
>computer acct, it cannot be used for this type of authentication.
>
>A user does not "log onto specific resources of a domain", a user is
>authenticated by a domain controller (DC) to use domain resources, and that
>authentication requires a domain user acct (a user always logs on "locally",
>but he/she can be authenticated either locally or by a DC).
>Generally, domain user acct authentication occurs when the user logs on to
>his ws, and that ws has connectivity with a DC. Note that this is a
>different authentication from the computer acct authentication mentioned
>above.
>A user on Home cannot be domain user acct authenticated by a DC during user
>logon to Home.
>However, when the user on Home attempts to use a domain resource, the domain
>server for that resource can contact a DC for domain user acct
>authentication. If the authentication is successful, then the normal domain
>user controls apply (user rights, share perms, NTFS perms).
>
>The phrase "with the administrator's permission" is misleading. Generally,
>the domain administrator does not have to do anything different to setup a
>domain user acct used by a Home user from what he/she would do for a user
>logging in locally to a XP Pro ws that is a domain member.
>
>I use Home in various domain setups, and it works great, provided a domain
>user acct was used to logon locally to Home. What a domain user on Home
>cannot do is receive domain GPO, and he/she cannot query AD.
>
>A DC authenticated domain user logged onto Home can use the following domain
>resources:
>NetBIOS networking
>non-NetBT networking
>Exchange server
>ISA
>
>
>
>> Inst their a 3 party application that will allow all this with home?
Brian:
Not that I am aware of.
There seems to be a popular misunderstanding that domain membership is
required to use domain resources. It is not required.
From a ws viewpoint, domain membership is about centralized mgmt of
computers, and it has some impt security implications.
However, the basic domain security concept is a domain user acct and what
entitlements that acct has via user acct settings, user rights, and
permissions.
Therefore, not being a domain member is not a barrier to using domain
resources. However, not having a domain user acct is a barrier.
A non-domain member computer with a domain authenticated user logon can use
the following domain resources:
DHCP
DNS
WINS
NetBIOS networking
non-NetBT networking
VPN
Exchange server
ISA
And in a SBS2k3 domain:
CompanyWeb
OWA
RWW
In a sense, to a ws user, domain membership means very little.
Brian Coats
April 7th 04, 02:43 PM
Hey cz? Inst their a 3 party application that will allow all this
with home?
>On Fri, 2 Apr 2004 07:53:31 -0800, "CZ" > wrote:
>>> Home cannot 'join' a domain on a domain based net. It can work happily
>on a work group one, and can log onto specific resources of a domain
>with the administrator's permission, just like Win98 can. You have to
>decide if that is adequate for your needs
>
>Alex:
>
>Joining a domain means that the ws can have a computer acct in the domain
>Active Directory (AD), and that the ws can receive Domain Admins gp and
>Domain Users gp into the local ws SAM. Home cannot do either, so Home
>cannot join a domain.
>Note that generally, the computer acct is authenticated by a domain
>controller (DC) during a user's local logon to a domain member computer when
>that computer has connectivity with a DC. Since Home cannot have a domain
>computer acct, it cannot be used for this type of authentication.
>
>A user does not "log onto specific resources of a domain", a user is
>authenticated by a domain controller (DC) to use domain resources, and that
>authentication requires a domain user acct (a user always logs on "locally",
>but he/she can be authenticated either locally or by a DC).
>Generally, domain user acct authentication occurs when the user logs on to
>his ws, and that ws has connectivity with a DC. Note that this is a
>different authentication from the computer acct authentication mentioned
>above.
>A user on Home cannot be domain user acct authenticated by a DC during user
>logon to Home.
>However, when the user on Home attempts to use a domain resource, the domain
>server for that resource can contact a DC for domain user acct
>authentication. If the authentication is successful, then the normal domain
>user controls apply (user rights, share perms, NTFS perms).
>
>The phrase "with the administrator's permission" is misleading. Generally,
>the domain administrator does not have to do anything different to setup a
>domain user acct used by a Home user from what he/she would do for a user
>logging in locally to a XP Pro ws that is a domain member.
>
>I use Home in various domain setups, and it works great, provided a domain
>user acct was used to logon locally to Home. What a domain user on Home
>cannot do is receive domain GPO, and he/she cannot query AD.
>
>A DC authenticated domain user logged onto Home can use the following domain
>resources:
>NetBIOS networking
>non-NetBT networking
>Exchange server
>ISA
>
>
>
Brian Coats
April 7th 04, 02:55 PM
Hey cz? Inst their a 3 party application that will allow all this
with home?
>On Fri, 2 Apr 2004 07:53:31 -0800, "CZ" > wrote:
>>> Home cannot 'join' a domain on a domain based net. It can work happily
>on a work group one, and can log onto specific resources of a domain
>with the administrator's permission, just like Win98 can. You have to
>decide if that is adequate for your needs
>
>Alex:
>
>Joining a domain means that the ws can have a computer acct in the domain
>Active Directory (AD), and that the ws can receive Domain Admins gp and
>Domain Users gp into the local ws SAM. Home cannot do either, so Home
>cannot join a domain.
>Note that generally, the computer acct is authenticated by a domain
>controller (DC) during a user's local logon to a domain member computer when
>that computer has connectivity with a DC. Since Home cannot have a domain
>computer acct, it cannot be used for this type of authentication.
>
>A user does not "log onto specific resources of a domain", a user is
>authenticated by a domain controller (DC) to use domain resources, and that
>authentication requires a domain user acct (a user always logs on "locally",
>but he/she can be authenticated either locally or by a DC).
>Generally, domain user acct authentication occurs when the user logs on to
>his ws, and that ws has connectivity with a DC. Note that this is a
>different authentication from the computer acct authentication mentioned
>above.
>A user on Home cannot be domain user acct authenticated by a DC during user
>logon to Home.
>However, when the user on Home attempts to use a domain resource, the domain
>server for that resource can contact a DC for domain user acct
>authentication. If the authentication is successful, then the normal domain
>user controls apply (user rights, share perms, NTFS perms).
>
>The phrase "with the administrator's permission" is misleading. Generally,
>the domain administrator does not have to do anything different to setup a
>domain user acct used by a Home user from what he/she would do for a user
>logging in locally to a XP Pro ws that is a domain member.
>
>I use Home in various domain setups, and it works great, provided a domain
>user acct was used to logon locally to Home. What a domain user on Home
>cannot do is receive domain GPO, and he/she cannot query AD.
>
>A DC authenticated domain user logged onto Home can use the following domain
>resources:
>NetBIOS networking
>non-NetBT networking
>Exchange server
>ISA
>
>
>
Brian Coats
April 7th 04, 05:55 PM
Hey cz? Inst their a 3 party application that will allow all this
with home?
>On Fri, 2 Apr 2004 07:53:31 -0800, "CZ" > wrote:
>>> Home cannot 'join' a domain on a domain based net. It can work happily
>on a work group one, and can log onto specific resources of a domain
>with the administrator's permission, just like Win98 can. You have to
>decide if that is adequate for your needs
>
>Alex:
>
>Joining a domain means that the ws can have a computer acct in the domain
>Active Directory (AD), and that the ws can receive Domain Admins gp and
>Domain Users gp into the local ws SAM. Home cannot do either, so Home
>cannot join a domain.
>Note that generally, the computer acct is authenticated by a domain
>controller (DC) during a user's local logon to a domain member computer when
>that computer has connectivity with a DC. Since Home cannot have a domain
>computer acct, it cannot be used for this type of authentication.
>
>A user does not "log onto specific resources of a domain", a user is
>authenticated by a domain controller (DC) to use domain resources, and that
>authentication requires a domain user acct (a user always logs on "locally",
>but he/she can be authenticated either locally or by a DC).
>Generally, domain user acct authentication occurs when the user logs on to
>his ws, and that ws has connectivity with a DC. Note that this is a
>different authentication from the computer acct authentication mentioned
>above.
>A user on Home cannot be domain user acct authenticated by a DC during user
>logon to Home.
>However, when the user on Home attempts to use a domain resource, the domain
>server for that resource can contact a DC for domain user acct
>authentication. If the authentication is successful, then the normal domain
>user controls apply (user rights, share perms, NTFS perms).
>
>The phrase "with the administrator's permission" is misleading. Generally,
>the domain administrator does not have to do anything different to setup a
>domain user acct used by a Home user from what he/she would do for a user
>logging in locally to a XP Pro ws that is a domain member.
>
>I use Home in various domain setups, and it works great, provided a domain
>user acct was used to logon locally to Home. What a domain user on Home
>cannot do is receive domain GPO, and he/she cannot query AD.
>
>A DC authenticated domain user logged onto Home can use the following domain
>resources:
>NetBIOS networking
>non-NetBT networking
>Exchange server
>ISA
>
>
>
>> Inst their a 3 party application that will allow all this with home?
Brian:
Not that I am aware of.
There seems to be a popular misunderstanding that domain membership is
required to use domain resources. It is not required.
From a ws viewpoint, domain membership is about centralized mgmt of
computers, and it has some impt security implications.
However, the basic domain security concept is a domain user acct and what
entitlements that acct has via user acct settings, user rights, and
permissions.
Therefore, not being a domain member is not a barrier to using domain
resources. However, not having a domain user acct is a barrier.
A non-domain member computer with a domain authenticated user logon can use
the following domain resources:
DHCP
DNS
WINS
NetBIOS networking
non-NetBT networking
VPN
Exchange server
ISA
And in a SBS2k3 domain:
CompanyWeb
OWA
RWW
In a sense, to a ws user, domain membership means very little.
>> Inst their a 3 party application that will allow all this with home?
Brian:
Not that I am aware of.
There seems to be a popular misunderstanding that domain membership is
required to use domain resources. It is not required.
From a ws viewpoint, domain membership is about centralized mgmt of
computers, and it has some impt security implications.
However, the basic domain security concept is a domain user acct and what
entitlements that acct has via user acct settings, user rights, and
permissions.
Therefore, not being a domain member is not a barrier to using domain
resources. However, not having a domain user acct is a barrier.
A non-domain member computer with a domain authenticated user logon can use
the following domain resources:
DHCP
DNS
WINS
NetBIOS networking
non-NetBT networking
VPN
Exchange server
ISA
And in a SBS2k3 domain:
CompanyWeb
OWA
RWW
In a sense, to a ws user, domain membership means very little.
>> Inst their a 3 party application that will allow all this with home?
Brian:
Not that I am aware of.
There seems to be a popular misunderstanding that domain membership is
required to use domain resources. It is not required.
From a ws viewpoint, domain membership is about centralized mgmt of
computers, and it has some impt security implications.
However, the basic domain security concept is a domain user acct and what
entitlements that acct has via user acct settings, user rights, and
permissions.
Therefore, not being a domain member is not a barrier to using domain
resources. However, not having a domain user acct is a barrier.
A non-domain member computer with a domain authenticated user logon can use
the following domain resources:
DHCP
DNS
WINS
NetBIOS networking
non-NetBT networking
VPN
Exchange server
ISA
And in a SBS2k3 domain:
CompanyWeb
OWA
RWW
In a sense, to a ws user, domain membership means very little.
>> Inst their a 3 party application that will allow all this with home?
Brian:
Not that I am aware of.
There seems to be a popular misunderstanding that domain membership is
required to use domain resources. It is not required.
From a ws viewpoint, domain membership is about centralized mgmt of
computers, and it has some impt security implications.
However, the basic domain security concept is a domain user acct and what
entitlements that acct has via user acct settings, user rights, and
permissions.
Therefore, not being a domain member is not a barrier to using domain
resources. However, not having a domain user acct is a barrier.
A non-domain member computer with a domain authenticated user logon can use
the following domain resources:
DHCP
DNS
WINS
NetBIOS networking
non-NetBT networking
VPN
Exchange server
ISA
And in a SBS2k3 domain:
CompanyWeb
OWA
RWW
In a sense, to a ws user, domain membership means very little.
>> Inst their a 3 party application that will allow all this with home?
Brian:
Not that I am aware of.
There seems to be a popular misunderstanding that domain membership is
required to use domain resources. It is not required.
From a ws viewpoint, domain membership is about centralized mgmt of
computers, and it has some impt security implications.
However, the basic domain security concept is a domain user acct and what
entitlements that acct has via user acct settings, user rights, and
permissions.
Therefore, not being a domain member is not a barrier to using domain
resources. However, not having a domain user acct is a barrier.
A non-domain member computer with a domain authenticated user logon can use
the following domain resources:
DHCP
DNS
WINS
NetBIOS networking
non-NetBT networking
VPN
Exchange server
ISA
And in a SBS2k3 domain:
CompanyWeb
OWA
RWW
In a sense, to a ws user, domain membership means very little.
>> Inst their a 3 party application that will allow all this with home?
Brian:
Not that I am aware of.
There seems to be a popular misunderstanding that domain membership is
required to use domain resources. It is not required.
From a ws viewpoint, domain membership is about centralized mgmt of
computers, and it has some impt security implications.
However, the basic domain security concept is a domain user acct and what
entitlements that acct has via user acct settings, user rights, and
permissions.
Therefore, not being a domain member is not a barrier to using domain
resources. However, not having a domain user acct is a barrier.
A non-domain member computer with a domain authenticated user logon can use
the following domain resources:
DHCP
DNS
WINS
NetBIOS networking
non-NetBT networking
VPN
Exchange server
ISA
And in a SBS2k3 domain:
CompanyWeb
OWA
RWW
In a sense, to a ws user, domain membership means very little.
>> Inst their a 3 party application that will allow all this with home?
Brian:
Not that I am aware of.
There seems to be a popular misunderstanding that domain membership is
required to use domain resources. It is not required.
From a ws viewpoint, domain membership is about centralized mgmt of
computers, and it has some impt security implications.
However, the basic domain security concept is a domain user acct and what
entitlements that acct has via user acct settings, user rights, and
permissions.
Therefore, not being a domain member is not a barrier to using domain
resources. However, not having a domain user acct is a barrier.
A non-domain member computer with a domain authenticated user logon can use
the following domain resources:
DHCP
DNS
WINS
NetBIOS networking
non-NetBT networking
VPN
Exchange server
ISA
And in a SBS2k3 domain:
CompanyWeb
OWA
RWW
In a sense, to a ws user, domain membership means very little.
>> Inst their a 3 party application that will allow all this with home?
Brian:
Not that I am aware of.
There seems to be a popular misunderstanding that domain membership is
required to use domain resources. It is not required.
From a ws viewpoint, domain membership is about centralized mgmt of
computers, and it has some impt security implications.
However, the basic domain security concept is a domain user acct and what
entitlements that acct has via user acct settings, user rights, and
permissions.
Therefore, not being a domain member is not a barrier to using domain
resources. However, not having a domain user acct is a barrier.
A non-domain member computer with a domain authenticated user logon can use
the following domain resources:
DHCP
DNS
WINS
NetBIOS networking
non-NetBT networking
VPN
Exchange server
ISA
And in a SBS2k3 domain:
CompanyWeb
OWA
RWW
In a sense, to a ws user, domain membership means very little.
Phil \(a.k.a. purplehaz\)
April 20th 04, 03:50 PM
CZ wrote:
>>> Note: xp home can be tweaked so you can browse a domain network
>>> without joining it.
>
>
> Phil:
>
> Home does not require any tweaking to use domain resources.
>
> I use Home in a domain for the following:
> NetBIOS networking
> non-NetBT networking
> Exchange server
> ISA
>
>
> Home cannot receive domain GPO, and Home cannot query AD.
Thanks for the info.
Phil \(a.k.a. purplehaz\)
April 20th 04, 04:54 PM
CZ wrote:
>>> Note: xp home can be tweaked so you can browse a domain network
>>> without joining it.
>
>
> Phil:
>
> Home does not require any tweaking to use domain resources.
>
> I use Home in a domain for the following:
> NetBIOS networking
> non-NetBT networking
> Exchange server
> ISA
>
>
> Home cannot receive domain GPO, and Home cannot query AD.
Thanks for the info.
vBulletin® v3.6.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.