Hot answers tagged windows-server-2003
Forest and Domain are two separate things. Open the Active Directory Domains and Trusts MMC. Right-click on the top node in the tree (Active Directory Domains and Trusts [yourdc]) and pick "Raise Forest Functional Level...".
To raise the forest functional level Open Active Directory Domains and Trusts. In the console tree, right-click the Active Directory Domains and Trusts node, and then click Raise Forest Functional Level. In Select an available forest functional level, click Windows Server 2003, and then click Raise. ...
Rob, the other two answers are correct. I think you have missed the difference between where you are clicking. See the screen shots below. Forest: Right Click at the very top Domain: Right click on the domain name
I had the same issue. Once I modified secpol.msc to these settings, it worked: Network security: LAN Manager authenitcation level - Not Defined Network security: Minimum session security for NTLM SSP based (including secure RPC) clients - Require 128-bit encryption Network security: Minimum session security for NTLM SSP based (including secure RPC) servers ...
I've been bashing my ahead against this wall for a few hours myself, and then it finally came to me: You may be in the wrong /Framework/ directory. I was in /Framework64/ and having these exact issues, but once I switched to /Framework/, aspnet_regiis -iru ran perfectly.
I had similar symptoms, not on a VM but a Win7 Laptop. Taskmgr.exe and other processes (like Winmerge.exe) were taking 13% of cpu (one out of 8). The issue was temporarily alleviated by restart, so I was doing that a lot. After long time investigating it, I figured that that Webroot Secure Anywere (software for virus and other types of protection) ...
This has been asked here for member servers being added only. If you want to make the 2008 box a DC you will need to use ADPREP link here. We have a 2003 domain functional level with 2008 members and DC's. All have GPO's applied created from 2008 and 2003 DC's, hope that helps.
The hard evidence is lack of support coming in very soon. But migrating a complicated set of servers to a new platform is a tricky business - so the sooner you start it, the better. You might want to try it on one machine first, and build up on your experience. And since R2 has been out for some time, now is the time to do it.
Only top voted, non community-wiki answers of a minimum length are eligible