Archived from groups: microsoft.public.windowsxp.customize (More info?)
Hello,
I've got a user that travels with his xp pro laptop. He works in 2
different offices, each with a different windows domain. One domain is
Server 2000, the other Server 2003. Is there anyway I can create a
seperate profile for each domain? Ideally a boot option that he could
select the Server 2000 domain, and fully log in as a member of that
domain; or select the Server 2003 domain and log in as a member of
that domain. I don't think such a thing is possible within Windows,
but maybe someone knows of a reliable 3rd-party app.
Thanks!
Archived from groups: microsoft.public.windowsxp.customize (More info?)
Judge Dredd wrote:
> I've got a user that travels with his xp pro laptop. He works in 2
> different offices, each with a different windows domain. One domain is
> Server 2000, the other Server 2003. Is there anyway I can create a
> seperate profile for each domain? Ideally a boot option that he could
> select the Server 2000 domain, and fully log in as a member of that
> domain; or select the Server 2003 domain and log in as a member of
> that domain. I don't think such a thing is possible within Windows,
> but maybe someone knows of a reliable 3rd-party app.
Is there some reason he has to be a member of either domain?
Couldn't he just be setup with proper local scripts that he would run to
connect to the resources given by one domain or another depending on which
script/where he was?
Archived from groups: microsoft.public.windowsxp.customize (More info?)
So I could remove his laptop from the domain, and set it up as a
workgroup. Then, create log-in scripts that he could run depending on
which company his is at? That way he would only have one profile, but
could use it at each office? That sounds like a good solution to this
problem: Simple and no new software to install. I had not thought of
that, obviously. Thanks for the suggestion.
On Tue, 2 Aug 2005 08:16:08 -0500, "Shenan Stanley"
<newshelper@gmail.com> wrote:
>Judge Dredd wrote:
>> I've got a user that travels with his xp pro laptop. He works in 2
>> different offices, each with a different windows domain. One domain is
>> Server 2000, the other Server 2003. Is there anyway I can create a
>> seperate profile for each domain? Ideally a boot option that he could
>> select the Server 2000 domain, and fully log in as a member of that
>> domain; or select the Server 2003 domain and log in as a member of
>> that domain. I don't think such a thing is possible within Windows,
>> but maybe someone knows of a reliable 3rd-party app.
>
>Is there some reason he has to be a member of either domain?
>Couldn't he just be setup with proper local scripts that he would run to
>connect to the resources given by one domain or another depending on which
>script/where he was?
>
>--
>Shenan Stanley
> MS-MVP
Archived from groups: microsoft.public.windowsxp.customize (More info?)
Judge Dredd wrote:
> I've got a user that travels with his xp pro laptop. He works in 2
> different offices, each with a different windows domain. One domain
> is Server 2000, the other Server 2003. Is there anyway I can create
> a seperate profile for each domain? Ideally a boot option that he
> could select the Server 2000 domain, and fully log in as a member
> of that domain; or select the Server 2003 domain and log in as a
> member of that domain. I don't think such a thing is possible
> within Windows, but maybe someone knows of a reliable 3rd-party app.
Shenan Stanley wrote:
> Is there some reason he has to be a member of either domain?
> Couldn't he just be setup with proper local scripts that he would
> run to connect to the resources given by one domain or another
> depending on which script/where he was?
Judge Dredd wrote:
> So I could remove his laptop from the domain, and set it up as a
> workgroup. Then, create log-in scripts that he could run depending on
> which company his is at? That way he would only have one profile, but
> could use it at each office? That sounds like a good solution to this
> problem: Simple and no new software to install. I had not thought of
> that, obviously. Thanks for the suggestion.
Most domain resources (unless the domain has REALLY been secured to a higher
level) can be accessed by anyone with the right credentials.
All you need to remember is that the username/password will have to be
presented in the "DOMAINNAME\username/password" fashion instead of just
"username/password". Printers, shares, etc can all be accessed in this
manner.
Archived from groups: microsoft.public.windowsxp.customize (More info?)
This is kinda of built in to Windows already. If you click on the "More
Options"/"Advanced" or whatever that button is on the lower right of the
login screen is labeled it will show the domain that is being logged into.
He then just choosed which of the two domains he wants to log in to from the
drop down menu. If they are not listed, then he just has type it in the
domain once and it should be listed next time.
It will then create a separate profile for each user account even if the
usernames are the same. If they are different username Windows will simply
create profiles called UserA and UserB, but if they are the same windows
will create profiles called UserA.DomainA and UserA.DomainB.
Jody C.
"Judge Dredd" <jd@megacityone.com> wrote in message
news:b4uue1h480mc4us49686subi7ri3l28q2e@4ax.com...
> So I could remove his laptop from the domain, and set it up as a
> workgroup. Then, create log-in scripts that he could run depending on
> which company his is at? That way he would only have one profile, but
> could use it at each office? That sounds like a good solution to this
> problem: Simple and no new software to install. I had not thought of
> that, obviously. Thanks for the suggestion.
>
>
> On Tue, 2 Aug 2005 08:16:08 -0500, "Shenan Stanley"
> <newshelper@gmail.com> wrote:
>
>>Judge Dredd wrote:
>>> I've got a user that travels with his xp pro laptop. He works in 2
>>> different offices, each with a different windows domain. One domain is
>>> Server 2000, the other Server 2003. Is there anyway I can create a
>>> seperate profile for each domain? Ideally a boot option that he could
>>> select the Server 2000 domain, and fully log in as a member of that
>>> domain; or select the Server 2003 domain and log in as a member of
>>> that domain. I don't think such a thing is possible within Windows,
>>> but maybe someone knows of a reliable 3rd-party app.
>>
>>Is there some reason he has to be a member of either domain?
>>Couldn't he just be setup with proper local scripts that he would run to
>>connect to the resources given by one domain or another depending on which
>>script/where he was?
>>
>>--
>>Shenan Stanley
>> MS-MVP
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.