Archive for category Server
Users, Computers, or Servers Do Not Display in the SBS 2008 Console
The SBS 2008 installation creates it’s own OUs. The Users, Computers, or Servers must be listed under these OUs in order for them to appear in the SBS 2008 Console.
No Support For Exchange 2007 On 2008 R2
Posted by JBrokaw in Exchange 2007, Server 2008 on September 16, 2009
From the MS Exchange Team Blog:
Exchange Server 2007 is not supported on Windows Server 2008 R2. However, Exchange 2007 SP1 RU9 and SP2 are supported against Windows Server 2008 R2 Active Directory servers. In addition, Exchange 2007 SP1 RU9 and SP2 are supported in Active Directory environments whose domain/forest functional levels have been raised to Windows Server 2008 R2.
From MS Technet:
Installing The First 2008 R2 DC on an Existing Domain
Posted by JBrokaw in Server 2008 on September 7, 2009
Prep the existing domain for a 2008 R2 DC.
- From the Windows Schema Master. Insert the R2 media.
- From the Windows Command Prompt. Change to the Support\Adprep folder.
- The Adprep folder has adprep for x64 servers and adprep32 for x32 servers.
- Enter: adprep /forestprep and C to continue.
- The Schema is updated with the R2 entries.
- When the update is finished. Run Adprep /domainprep /gpprep on the Infrastructure Operations Master.
Some of What’s New in Windows Server 2008 R2
Posted by JBrokaw in Server 2008 on September 7, 2009
Server 2008 R2 is now a 64bit only OS.
Updated Hyper-V.
- Now supports “Live Migration”. The MS answer to VMware VMotion.
- Requires the use of Windows Failover Clustering, Clustering Services, and Shared Volume technology.
Active Directory Administrative Center.
- Provides a task-driven interface for managing AD.
- ADAC is meant to replace AD Users and Computers, Sites and Services, and Domains and Trusts. The original management tools are still available.
- ADAC is automatically installed when a 2008 R2 servers is promoted to a DC.
- ADAC currently only runs on Server 2008 R2.
Managed Service Accounts.
- Designed to provide crucial applications such as SQL Server or IIS with the isolation of their own accounts, while eliminating the need for an administrator to manually administer the SPN and credentials for these accounts.
Offline Domain Join.
- Allows a client PC to join a domain without being connected to the domain.
AD Recycle Bin.
- Allows deleted AD objects to be restored.
- Requires Server 2008 R2 forest functional level.
Server Manager.
- Server Manager is now able to manage local and remote Server 2008 servers.
Terminal Services is now Remote Desktop Services.
- The new RemoteApp and Desktop Connection support Aero Glass, multi-monitor support, multimedia redirection, audio recording, and DirectX 9,10, and 11 redirection.
PowerShell 2.0.
.Net Framework support in Server Core.
- Server Core still does not support SQL Server or Exchange.
IIS 7.5.
Core Parking.
- Allows the OS to dynamically control the number of cores used. Unused cores can be put into sleep mode to reduce power.
- Can be controlled through new GPO settings.
ACPI P-states.
- Allows running CPUs at lower CPU speeds and reduce power consumption.
- Can be controlled through new GPO settings.
Domain Name System Security Extensions (DNSSEC).
Read-Only DFS Support.
Windows Deployment Services.
- Dynamic Driver Provisioning: Add driver images prior to deployment.
- Virtual Hard Disk Deployment.
- Additional Multicasting.
- PXE Provider For Transport Server.
- Additional EFI Functionality.
New Biometric Support.
File Server Resource Manager.
- File Classification.
- File Management Tasks.
Find the rest of the additions to Server 2008 R2 – Here
SBS 2003 to SBS 2008 Migration
Verify SBS 2003 is running the most recent service packs.
1. To verify that your server is running Service Pack 1 for Windows Small Business Server 2003.
- Start the Registry Editor, and then locate the following registry entry:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinesServer\ServicePackNumber
- If the value is 0×00000001, Service Pack 1 (SP1) for Windows SBS 2003 is installed. Close the Registry Editor.
2. Verify that your server is running Service Pack 2 for Windows Server 2003.
3. Verify that your server is running Service Pack 2 for Exchange Server 2003.
4. Verify that your server is running Service Pack 3 for Windows SharePoint Services 2.0
- Click Start, click Control Panel, and then click Add or Remove Programs.
- Click Microsoft Windows SharePoint Services 2.0, and then click Click here for support information. If the version number is 11.0.8173.0, SP3 for Windows SharePoint Services 2.0 is installed.
5. Verify that Service Pack 1 for Microsoft Core XML Services (MSXML) 6.0 is installed
- On the Source Server, verify that MSXML6.dll is version 6.10.1129.0 or higher. MSXML6.dll is in the %SystemDrive%:\Windows\System32 folder.
6. Verify that .NET Framework 2.0 is installed.
7. Raise the functional level of the source domain and the forest to Windows Server 2003.
How to Deploy a Windows 2008 Server From a Template with vSphere
Posted by JBrokaw in Server 2008, VMware on August 13, 2009
Windows 2000/2003 Export/Import DHCP Database
Posted by JBrokaw in Server 2000, Server 2003 on July 29, 2009
For Windows 2000: Download and install the DHCPExim tool. Export/Import the DHCP Database config. Note: this tool is only supported on Windows 2000. Using this tool on Windows 2003 will generate an error.
To Import the data from a Windows 2000 Server to a Windows 2003 Server. From a command prompt: netsh dhcp server import c:\filename.txt all
To Import/Export to and from a Windows 2003 Server:
Command to Export DHCP Data – netsh dhcp server export C:\filename.txt all
Command to Import DHCP Data – netsh dhcp server import c:\filename.txt all
EventID 26 & 27
Ran into this error today logged every couple of hours in the event log.
Event Type: Error
Event Source: KDC
Event Category: None
Event ID: 26
Date: 11/11/2008
Time: 7:33:29 AM
User: N/A
Computer: ADGREENTEST2
Description:
While processing an AS request for target service krbtgt, the account MITC0312$ did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 2). The requested etypes were 18. The accounts available etypes were 23 -133 -128 3 1 -140.
I found this response from MS on the technet site.
Kerberos authentication protocol is significantly improved in Windows Vista with the following features
- AES support
- Improved security for Kerberos Key Distribution Centers (KDCs) located on branch office domain controllers
Typically, when the parties are operating systems running Windows Vista or Windows Server 2008, the exchange will use AES. However, if one of the parties is an operating system running Windows 2000 Professional, Windows 2000 Server, Windows XP, or Windows Server 2003, the exchange will not use AES.
Based on your configuration, Vista client, Windows Server 2003 DC as KDC, the cause of the KDC event 26/27 is the client computer sends the service ticket request with Etype which is not supported by Windows 2003 DC but supported by Windows 2008 DC. The error that is being logged on the Windows 2003 domain controller can safely be ignored as it is by design. The domain controller is just informing the client what Etypes it supports. Vista clients are then falling back to the supported types.
Printer Deployment With Group Policy
Posted by JBrokaw in SBS 2008, Server 2008 on June 23, 2009
Create a new GPO under Group Policy Management
Assign the Printer based on Computer or User Configuration.
- Expand Preferences – Control Panel Settings – Printers – Assign New Printers
For Windows XP Clients follow the steps below:
Install update on XP Clients to support 2008 Preferences. (http://support.microsoft.com/kb/943729)
To use the PushPrinterConnections.exe file
1. Using Group Policy Management console (gpmc.msc), right-click the GPO with your printer connections settings, and then click Edit.
2. In the Group Policy Object Editor tree, navigate to one following locations:
"If the printer connections are deployed per-machine, go to Computer Configuration, Windows Settings, Scripts (Startup/Shutdown).
"If the printer connections are deployed per-user, go to User Configuration, Windows Settings, Scripts (Logon/Logoff).
3. Right-click Startup or Logon, and then click Properties.
4. In the Logon Properties or Startup Properties dialog box, click Show Files.
5. Copy the PushPrinterConnections.exe file to this location and then close the window.
6. In the Logon Properties or Startup Properties dialog box, click Add.
7. Type PushPrinterConnections.exe in the Script Name box.
8. If you want to enable logging, type log in the Script Parameters box. Log files are written to %windir%\temp\ppcMachine.log (for per-computer connections) and %temp%\ppcUser.log (for per-user connections) on the computer on which the policy is applied.
9. Click OK.
Network Requirements for SBS 2008 Migration
The SBS 2008 getting started wizards assume that the server will be in a Class C subnet (i.e., subnet with a mask of 255.255.255.0). Furthermore, when you run the Connect to the Internet wizard, the wizard specifically looks for your Internet gateway at specific addresses in the 192.168.x.x class C subnet. So what if you’re migrating from an existing SBS 2003 server that doesn’t match one of these assumptions?
In the case of your existing server being in a subnet other than 192.168.x.x, no problem. When you create the answer file, you’ll plug in the IP addresses for the existing server, the IP gateway, and the new server into the Answer File Creator so that the migration setup can do its job. In the case of a new installation, the Connect to the Internet wizard will fail to automatically detect the router and you’ll be able to enter the information manually.
But if your network is on anything other than a Class C subnet, migration is not going to work. You will have to temporarily configure the network into a Class C setup to get the initial migration working. After that, you can modify the network settings to go back to your other network configuration, but the migration setup requires a Class C configuration in order to work.