1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Introducing TS 2003 64bit to 32bit farm

Discussion in 'Windows Home Server' started by MBernal, Aug 18, 2009.

  1. MBernal

    MBernal Guest

    I have a Windows 2003 AD network with a 3 server TS 2003 32bit farm. Roaming
    profiles and redirected folders are used. Are there issues with introducing a
    Windows 2003 64bit server with Terminal Services? I suspect that if i were to
    create this new TS2003 64bit server and logon with an existing roaming
    profile, that it might modify the profile and/or ntuser.dat, and make it
    unusable when logging back onto my TS 2003 32 bit server.
     
  2. the only problem I have seen is around the imho the stupid Program Files vs
    Program Files (x86) folders. If you applications are 32 bit and you install
    them on the x64 box they will go into the (x86) folder tree. That is not
    really a problem until your farm uses a common start menu shortcut for all
    users and the application will now not launch on the all servers correctly
    because the shortcut folder is not the same on x86 vs x64. If your
    applications have both a x86 and x64 version that this is not an issue.


    "MBernal" <MBernal@discussions.microsoft.com> wrote in message
    news:9E294706-8494-4EEF-82E8-B932A9A58680@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > I have a Windows 2003 AD network with a 3 server TS 2003 32bit farm.
    > Roaming
    > profiles and redirected folders are used. Are there issues with
    > introducing a
    > Windows 2003 64bit server with Terminal Services? I suspect that if i were
    > to
    > create this new TS2003 64bit server and logon with an existing roaming
    > profile, that it might modify the profile and/or ntuser.dat, and make it
    > unusable when logging back onto my TS 2003 32 bit server. <!--colorc--><!--/colorc-->
     
  3. User profile design has changed with Vista and Windows 2008. Here's
    information about the new Version 2 user profiles and how to
    migrate from Version 1 (XP, 2003) profiles to Version 2 profiles:

    947025 - Support guidelines for migrating roaming user profiles
    data to Windows Vista or to Windows Server 2008


    _________________________________________________________
    Vera Noest
    MCSE, CCEA, Microsoft MVP - Terminal Services
    RDS troubleshooting:

    ___ please respond in newsgroup, NOT by private email ___


    "Jerry Alan Braga" <jerry.braga@hotmail.com> wrote on 18 aug 2009
    in microsoft.public.windows.terminal_services:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > the only problem I have seen is around the imho the stupid
    > Program Files vs Program Files (x86) folders. If you
    > applications are 32 bit and you install them on the x64 box they
    > will go into the (x86) folder tree. That is not really a
    > problem until your farm uses a common start menu shortcut for
    > all users and the application will now not launch on the all
    > servers correctly because the shortcut folder is not the same on
    > x86 vs x64. If your applications have both a x86 and x64
    > version that this is not an issue.
    >
    >
    > "MBernal" <MBernal@discussions.microsoft.com> wrote in message
    > news:9E294706-8494-4EEF-82E8-B932A9A58680@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> I have a Windows 2003 AD network with a 3 server TS 2003 32bit
    >> farm. Roaming
    >> profiles and redirected folders are used. Are there issues with
    >> introducing a
    >> Windows 2003 64bit server with Terminal Services? I suspect
    >> that if i were to
    >> create this new TS2003 64bit server and logon with an existing
    >> roaming profile, that it might modify the profile and/or
    >> ntuser.dat, and make it unusable when logging back onto my TS
    >> 2003 32 bit server. <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
     

Share This Page