Terminal Server - Disaster Recover

  • Thread starter Thread starter SJMP
  • Start date Start date
S

SJMP

Guest
I am setting up my off-site disaster recovery terminal server.

1 - Is there anyway to migrate profiles from the production server? Or just
copy and paste them when everyone is logged off?
2 - Licensing - I have licenses for my current server. How can I get those
licenses installed on the DR Terminal Server (non-active) until I have to
activate them? I am hoping that I dont have to put in a call to Microsoft if
I needed to activate this server in an emergency.

Thanks in advance!

SJMP
 
Re: Terminal Server - Disaster Recover

What version of server are we talking about?

1) Not without a 3rd party tool from like Quest software. You cannot
simply copy profiles as parts of the computers registry has information on
what account is associated to what profile folders. It does not simply look
at name of the folder.

2) Your best bet would be to leave your DR "farm" in per user licensing
mode (if we're talking Win2k3). Other than that, I've seen people say
they've backed up and restored the licensing database but I've also seen
nothing to confirm that this actually works. Yes, you would have to call
the MS clearinghouse otherwise to get your licenses migrated.

--
Jeff Pitsch
Microsoft MVP - Terminal Services

"SJMP" <sjmp@newsgroup.nospam> wrote in message
news:13B2A4EB-E605-42CD-8C53-16B9419CD7DC@microsoft.com...
>I am setting up my off-site disaster recovery terminal server.
>
> 1 - Is there anyway to migrate profiles from the production server? Or
> just
> copy and paste them when everyone is logged off?
> 2 - Licensing - I have licenses for my current server. How can I get those
> licenses installed on the DR Terminal Server (non-active) until I have to
> activate them? I am hoping that I dont have to put in a call to Microsoft
> if
> I needed to activate this server in an emergency.
>
> Thanks in advance!
>
> SJMP
 
Re: Terminal Server - Disaster Recover

Our TS License Server is virtualized, and we clone a copy to our DR location
every 2 weeks. This way if our primary site were to go dark, we can just
bring up the Clone at DR, and move on. We do a quarterly Dr test to confirm
all of our environment is ready to go should it need be.

"Jeff Pitsch" wrote:

> What version of server are we talking about?
>
> 1) Not without a 3rd party tool from like Quest software. You cannot
> simply copy profiles as parts of the computers registry has information on
> what account is associated to what profile folders. It does not simply look
> at name of the folder.
>
> 2) Your best bet would be to leave your DR "farm" in per user licensing
> mode (if we're talking Win2k3). Other than that, I've seen people say
> they've backed up and restored the licensing database but I've also seen
> nothing to confirm that this actually works. Yes, you would have to call
> the MS clearinghouse otherwise to get your licenses migrated.
>
> --
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> "SJMP" <sjmp@newsgroup.nospam> wrote in message
> news:13B2A4EB-E605-42CD-8C53-16B9419CD7DC@microsoft.com...
> >I am setting up my off-site disaster recovery terminal server.
> >
> > 1 - Is there anyway to migrate profiles from the production server? Or
> > just
> > copy and paste them when everyone is logged off?
> > 2 - Licensing - I have licenses for my current server. How can I get those
> > licenses installed on the DR Terminal Server (non-active) until I have to
> > activate them? I am hoping that I dont have to put in a call to Microsoft
> > if
> > I needed to activate this server in an emergency.
> >
> > Thanks in advance!
> >
> > SJMP
>
>
>
 
Re: Terminal Server - Disaster Recover

then there hsould be nothing you have to do except point the DR terminal
server to the license server.

--
Jeff Pitsch
Microsoft MVP - Terminal Services

"Larryw" <Larryw@discussions.microsoft.com> wrote in message
news:1A449416-FFFA-49C7-959F-CE3E6CDC06A7@microsoft.com...
> Our TS License Server is virtualized, and we clone a copy to our DR
> location
> every 2 weeks. This way if our primary site were to go dark, we can just
> bring up the Clone at DR, and move on. We do a quarterly Dr test to
> confirm
> all of our environment is ready to go should it need be.
>
> "Jeff Pitsch" wrote:
>
>> What version of server are we talking about?
>>
>> 1) Not without a 3rd party tool from like Quest software. You cannot
>> simply copy profiles as parts of the computers registry has information
>> on
>> what account is associated to what profile folders. It does not simply
>> look
>> at name of the folder.
>>
>> 2) Your best bet would be to leave your DR "farm" in per user licensing
>> mode (if we're talking Win2k3). Other than that, I've seen people say
>> they've backed up and restored the licensing database but I've also seen
>> nothing to confirm that this actually works. Yes, you would have to call
>> the MS clearinghouse otherwise to get your licenses migrated.
>>
>> --
>> Jeff Pitsch
>> Microsoft MVP - Terminal Services
>>
>> "SJMP" <sjmp@newsgroup.nospam> wrote in message
>> news:13B2A4EB-E605-42CD-8C53-16B9419CD7DC@microsoft.com...
>> >I am setting up my off-site disaster recovery terminal server.
>> >
>> > 1 - Is there anyway to migrate profiles from the production server? Or
>> > just
>> > copy and paste them when everyone is logged off?
>> > 2 - Licensing - I have licenses for my current server. How can I get
>> > those
>> > licenses installed on the DR Terminal Server (non-active) until I have
>> > to
>> > activate them? I am hoping that I dont have to put in a call to
>> > Microsoft
>> > if
>> > I needed to activate this server in an emergency.
>> >
>> > Thanks in advance!
>> >
>> > SJMP
>>
>>
>>
 
Back
Top