My-Technet

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.

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.

(continue reading…)

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.

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.

I found something else out that is enabled by default in SBS 2008. There is a folder storage limit setup on the SBS 2008 server by default. The Limit is 2GB. You can disable it by going into the properties of existing users under folders and disable the folder quota.

The “Standard User Template” has the Exchange 2gb quota and the 2gb Folder Quota enabled. You can disable it by Right Clicking on the “Standard User” Role then disable the two under E-Mail and Folders.

When you go to the new http://connect site, run the tool, and get to the section where you select the local profile to use for the specified domain account, you may find that the profile you want to choose is not listed in the drop-down list. This doesn’t mean that there’s a problem with the profile, just that the profile has probably been marked private.

The simple fix is to open Windows Explorer, browse to C:\Documents and Settings, right-click on the user’s folder, and clear the “Make Folder Private” checkbox. Apply the changes, close the window, and run the Connect Computer tool again. The profile should show in the list now. If it still does not, go back into the folder settings, enable the “Make Folder Private” checkbox, apply the changes, then disable the “Make Folder Private” checkbox and apply the changes again.