Sysprep question

[Sylvor]

Hi,

I am about to do some work for a client. I visited the site at the weekend and found out that they do not hold a licence for their Win2k server (their only server). They have purchased one which will hopefully arrive tomorrow... I do not want to have to reinstall windows and re-install all the apps and set-up active directory etc.

I have to change the key as they want to start using Terminal Services in application mode.

(Here comes the question!)

I was (am) hoping to use Sysprep to change the key, does anyone know if Sysprep will kill the active directory settings and other settings. I know I will have to reconfigure TCP/IP etc, but that's not too much of a drag.

Any help would be very much appreciated.

D

 

[ashpp]

Sysprep will remove all the domain information.

Try this

http://www.magicaljellybean.com/keyfinder.shtml

Make sure you charge them the earth to do it thou

 

[Sylvor]

Heya Ash,

Thanks for that - typical that it'll kill active directory I suppose!

MagicalJellybean does not allow you the option to change the product-key, only to view it. Viewing is not so much the problem, I know what the key is, I know it is not a key owned by the client.

Any other ideas on possible ways 'round this?

Dave!

 

[ashpp]

Are you sure, theres an option to Change Windows Key on it?

 

[Sylvor]

Niya,

Yes, there is an option, but it is only activated for earlier Windows versions. With 2000 Pro & Server the button is 'greyed'



Thanks for trying tho

 

[wolluf]

Do you actually need to change the key? 2k doesn't have activation - so if client now has a valid licence - surely any valid key is acceptable?

 

[Sylvor]

Wolluf,

Normally I'd say no. I think MS are happy enough for people to simply hold a license. But because I need to use Terminal Services in application mode - I think I have to have a proper key!

D

 

[SelbyGlenn]

Im a bit rusty on this but as far as I can remember the Terminal Server licenses are completely seperate to W2k Server licenses. You need to install Terminal Services Licensing on their server. This is where you install the Terminal Service licenses. You get a 30 day grace period initially anyway so you should just be able to install TS in app mode without first needing any licenses.

Having said that, if their workstations are running 2000 then I believe the connection is free and they do not have to purchase any CALS! But knowing Microshaft, this may well not be the case any more. Best to check.

Hope this helps.

Glenn
BEng MCSE CCA

 

[Sylvor]

Selby,

Yes, you are quite right about the grace period, although I think it is actually 90 days for the temporary license.

I was convinced that 2000 Professional clients (and later, ie: XP Pro) did not need a CAL, but I spoke with MS licensing and they said they need both a server CAL and a TS CAL.

Althought the MS site says something to the contrary:

"A built-in token is issued to a client that is running Windows 2000 Professional"

"Each device that initiates a Windows 2000 Terminal Services (application server mode) session must be licensed with the following:

Windows 2000 Professional license or Windows 2000 Terminal Services Client Access license.
Windows 2000 Server Client Access license or BackOffice family ® Client Access license."

Source: MS whitepaper on TS 2000 licensing! (Very confusing)

Anyway, I will call them a bit later and check about the product key for 2k - I think you can activate the TS CALs over the phone.

Dave

 

[SelbyGlenn]

That's the problem with MS; they keep moving the goal posts and changing the rules every five minutes! I would be interested to know what answer you get from MS.

Cheers,

Glenn
BEng MCSE CCA

 

[Davetoo]

If you have a Windows 2000 Server, and your clients are Windows 2000 Pro or Windows XP Pro, then you only need a CAL to access the server, you do not need a separate TS CAL.

If you have Windows 2003 Server, then you will need both a CAL for the server *and* a CAL for the TS, regardless of the client.

In either case, you don't need to worry about the W2K Key, as the TS CAL's are a completely separate installation. So as long as you have a proper license for the Server, you're ok. Install the TS License Server and appropriate CAL's for TS and you're set.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[Sylvor]

Excellent news about the Win2k product key. I really think MS should release some way of changing the key without affecting services too much, although I understand that some applications are related to these keys.

It wouldn't make any difference to piracy issues, it's only allow people who are unlicensed to get legal easier!

Though I suppose these things can always be exploited.

Thanks for the heads-up on the TS CALs, but I assure you, that is NOT at all what the MS licensing person told me! - We have bought 5 CALs now

Anyway, I will post back on this thread once I have finished all of this, just to let you know how it went

D

 

[Davetoo]

Sometimes the people on the phone don't have the right answers either. ;-)

Read this:

http://www.microsoft.com/windows2000/server/howtobuy/pricing/terminal.asp

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.