Prev: cant run this application
Next: Multiple Logon problem with session broker
From: Dragon on 10 May 2010 08:01
Thank you Meinolf.

"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
news:6cb2911deb618cc9653e511a04c(a)msnews.microsoft.com...
> Hello Dragon,
>
> You can run Windows server 2008 member machines without any problem in a
> Windows 2003 domain. Where you have to take care about is the new profile
> version 2 if the users logon to a Windows server 2008 machine, this is
> c:\users for example and the old profile version is c:\documents and
> settings, here you have to check before and test.
> http://support.microsoft.com/kb/947025
>
> http://blogs.technet.com/askds/archive/2008/06/17/user-profile-policies-in-windows-server-2008-and-windows-vista.aspx
>
> Existing features on Windows server 2003 R2 machines are not effected from
> installing another OS machine in the network.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Hi,
>>
>> We plan to install and configure Terminal Services / RemoteApp
>> functionality on a Server 2008 R2. All our other systems, including
>> domain are running Non-R2 version of server 2008 and some are running
>> 2003. Do you guys see any issues we might face? Is it even possible
>> without losing any R2 functionality related to Remote app in this
>> environment?
>>
>> Also, if someone could point me to a web link with this information
>> that would be great.
>>
>> Thanks.
>>
>
>
 | 
Pages: 1
Prev: cant run this application
Next: Multiple Logon problem with session broker