[THIN] Re: W2K and W2K3 NTUSER.DAT files
- From: "Joe Shonk" <joe.shonk@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Tue, 26 Feb 2008 16:46:10 -0700
All you need to do is create an New OU in AD, place your 2003 servers in
this OU and create a GPO that defines the Terminal Server Profile Path for
the machines in that OU.
Joe
On Tue, Feb 26, 2008 at 9:29 AM, Jensen, Jay <jjensen@xxxxxxxxx> wrote:
> Need your advice.
>
>
>
> Currently we run over 200 Windows 2000 PS 4.0 Terminal Servers and since
> we got approval and W2k3 TS Cal licenses, we can move to Windows 2003 TS
> servers prior to moving to PS 4.5 later this year. Here are some options
> that I believe can be done. We use Roaming Profile and the NTUSER.DATfile
> loaded will depend on if it a W2K or a W2K3
> NTUSER.DAT File.
>
>
>
> 1. Write a script to determine Windows 2000 or Windows 2003 so we can
> load the correct NTUSER.DAT profile, Log script will have to handle same
> issue saving the file to proper file structure.
>
> 2. Do a Flex Profile (Mandatory Profile with User defined registry
> keys). This is an issue with some of our applications.
>
>
>
> Does anyone have a sample script that they used when they moved from
> Windows 2000 TS to Windows 2003 TS servers?
>
>
>
> Thank You.
>
> Jay
>
Other related posts:
