Moving Data Folders for Windows Small Business Server 2003

Updated: November 12, 2009

Applies To: Windows SBS 2003

Objective

There are several reasons why you might want to move the data folders for the Microsoft® Windows® Small Business Server 2003 operating system. These folders include: Users Shared Folders, the Windows SharePoint® Services and Monitoring databases, Exchange databases and log files, Sent Faxes folder, and ClientApps shared folder. The reasons you might want to move these folders include:

  • The drive where the data folders for Windows Small Business Server 2003 are stored is running out of hard disk space.

  • You decide to add a higher performance disk or RAID array (redundant array of independent disks) to your server to use for data storage. In this case, you want to install the disk(s) and then move the data folders to the new disk(s).

  • The server was preinstalled by an Original Equipment Manufacturer (OEM) using one partition and you want to move the data to another drive.

  • You want the operating system on a separate drive than your data drive to make backup easier.

  • You want to move data to a separate partition to optimize performance of the volume where shadow copy is enabled.

The following key terms are associated with moving data folders for Windows Small Business Server 2003:

Source partition   The partition from which you are moving data folders.

Destination partition   The partition to which you are moving data folders.

Drive   An area of storage on a hard disk drive that is formatted with a files system and has a driver letter.

Partition   A portion of a physical disk that functions as if it were a physically separate disk. After you create a partition, you must format it and assign it a drive letter before you can store data on it. Once the partition is formatted, it is referred to as a partition. On basic disks, partitions are known as basic volumes, which include primary partitions and logical drives. On dynamic disks, partitions are known as dynamic volumes, which include simple, striped spanned, mirrored, and RAID-5 volumes.

Volume   An area of storage on a hard disk. A volume is formatted by using a file system, such as file allocation table (FAT) or the NTFS file system, and has a drive letter assigned to it. A single hard disk can have multiple volumes, and a volume can also span multiple disks.

WMSDE   SQL Server™ 2000 Desktop Engine (Windows) (WMSDE). Setup installs an instance of WMSDE for the Windows SharePoint Services database. WMSDE is a protected system database that is usable only by Windows components. There is no size limitation for a WMSDE database. A WMSDE database cannot be used by other applications and non-Microsoft applications.

MSDE 2000    SQL Server 2000 Desktop Engine (MSDE 2000). Setup installs an instance of MSDE 2000 for the Monitoring database. There is a 2 gigabyte (GB) size limitation for a MSDE 2000 database. An MSDE 2000 database can be used by other applications and non-Microsoft applications.

Overview of Moving Data Folders

This document provides step-by-step instructions for moving each of the data folders for Windows Small Business Server 2003. You can choose to move one or all of the data folders. For example, you can choose to move only the Users Shared Folders and no other data folders. Additionally, it is not necessary to move the data folders in the order presented in this document. For example, you can choose to move the Exchange databases and log files on one day and then the Users Shared Folders on another. However, it is strongly recommended that you always complete and verify a full backup before moving any data folders.

Consider the following before completing this document:

  • To complete the procedures in this document, you must be logged on as a member of the Domain Admins security group.

  • This document assumes that if you are moving the data folders to a new disk or new RAID array, the disk(s) are already physically installed in the computer running Windows Small Business Server 2003.

  • When moving data folders, the resource that uses the data folder will not be available. For example, while moving the Exchange databases and log files, users will not be able to send or receive e-mail. It is recommended that you move data folders when users are not connected to the network. However, if you must move folders while users are connected to the network, you must notify them to close resources that are affected by the moving of data folders

Moving data folders on the computer running Windows Small Business Server 2003 includes the following steps:

  • Step 1: Complete and Verify a Full Backup. The evening prior to moving data folders, back up the computer running Windows Small Business Server 2003 to protect your data from accidental loss in the unlikely event of an error occurring while moving data folders.

  • Step 2: Notify Users that Resources will be Unavailable. When moving data folders, the resource that uses that data folder will not be available.

  • Step 3: Move the Users Shared Folders. The Users Shared Folders is the folder where each user’s individual data folder is located. In addition, if redirection of My Documents is enabled, the My Documents are stored in each user’s data folder. Moving the Users Shared Folders requires several steps.

  • Step 4: Move the Windows SharePoint Services Databases. The Windows SharePoint Services databases use an instance of WMSDE. This is where the Company Web site documents are stored. Moving the databases requires several steps.

Note

This document provides step-by-step instructions for moving the databases when using the instance of WMSDE. If you upgraded the instance to use SQL Server 2000, see article 224071, "INF: Moving SQL Server Databases to a New Location with Detach/Attach," in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=4441).
If you are using SQL Server 2000 or SQL Server 2005, you can use the SQL Server Enterprise Manager to back up, detach, and attach a database. For more information about SQL Server Enterprise Manager, see "SQL Server Enterprise Manager" at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=102362).
For more information about backing up a database, see "How to create a database backup (Enterprise Manager)" at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=102363).
For more information about attaching and detaching a database, see "How to attach and detach a database (Enterprise Manager)" at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=102364).
For more information about moving SharePoint databases, see "Moving Windows SharePoint Services Databases" at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=102365).

  • Step 5: Move the Monitoring Instance of MSDE 2000. The Monitoring database uses an instance of MSDE 2000. This is where the information for the monitoring reports is stored. Moving the Monitoring instance of MSDE 2000 requires several steps.

  • Step 6: Move the Exchange Databases and Log Files. There are two Exchange databases, the mailbox store and public folder store, where users' mailboxes and folders are stored. The information about if messages are being transferred correctly and in a reasonable amount of time by the message transfer agent (MTA) is stored in the log files. To move the Exchange databases and log files, follow the Knowledge Base article referenced in the procedure.

  • Step 7: Move the Sent Faxes Folder. The Sent Faxes folder is where outgoing faxes are archived. To move the Sent Faxes folder, you need to change the location where sent faxes are archived, and then copy the existing sent faxes to the destination location.

  • Step 8: Move the ClientApps Data Folder. By default, the ClientApps shared folder takes up approximately 1 gigabyte (GB) of space. However, if you have added several applications to this folder that you are deploying using the Assign Applications Wizard, the folder might have grown considerably in size. In this case, you might want to move the ClientApps shared folder to another location.

  • Step 9: Move the Windows Server Update Services Folder. Updates are divided into two parts: a metadata part that describes the update, and the files required to install the update on a computer. Although metadata that describes updates is stored in the Windows Server Update Services (WSUS) database, the update files that are used to install the updates are stored in a folder on the server. You will use the Wsusutil.exe command to move the update files to a different location.

  • Step 10: Complete the Process. After moving the data folders, you should notify users that the resources are again available for use. Additionally, you should complete a full backup.

Step 1: Complete and Verify a Full Backup

To protect your data from accidental loss in the unlikely event of an error occurring while moving data folders, back up the computer running Windows Small Business Server 2003 the evening prior to moving data folders.

To complete and verify a full backup

  1. The evening prior to moving data folders, perform a full system backup. For more information about completing a backup, see “Backing Up and Restoring Windows Small Business Server 2003” at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=19525).

  2. Verify that the backup ran successfully. To test the integrity of the backup, select random files from your backup, restore them to an alternate location, and then confirm that the backed up files are the same as the original ones. If you used the Windows Small Business Server 2003 Backup Wizard, you can verify that the backup ran successfully through Server Management. (Click Start, click Server Management, and then click Backup. Information about the backup appears in the details pane.)

Step 2: Notify Users that Resources will be Unavailable

When moving each data folder, the resource that uses that data folder will not be available. If you plan to move any data folders while users are still connected to the network, you should notify them regarding which resources will be unavailable. For example, you could send an e-mail to users several days prior to moving the data folders to let them know what resources will be unavailable. You could then remind users the day of the move.

  • While moving the Users Shared Folders, the users will not be able to save to their existing user folders. Additionally, if users’ My Documents are being redirected to their user folders, they will not be able to access documents.

  • While moving the databases, the Company Web site will not be available to users. Users must save any open documents from the site and close any browser windows open to the Company Web site.

  • While moving the Exchange databases and log files, users will not be able to send or receive e-mail.

  • While moving the Sent Faxes folder, the archived faxes will not be available.

  • While moving the ClientApps shared folder, administrators will not be able to deploy applications and users will not be able to install applications.

Step 3: Move the Users Shared Folders

The Users Shared Folders is the folder where each user’s individual data folder is located. In addition, if redirection of My Documents is enabled, the My Documents are stored in each user’s data folder. Moving the Users Shared Folders requires the following steps:

  • Closing connections for Users Shared Folders

  • Ensuring the destination partition is formatted as NTFS

  • Enabling quotas on the destination partition

  • Exporting and importing quota settings

  • Moving the Users Shared Folders to the destination partition

  • Sharing the Users folder on the destination partition

  • Enabling file version retention on the destination partition

To close connections to Users Shared Folders

  1. Click Start, and then click Server Management.

  2. In the console tree, click Shares (Local).

  3. In the details pane, locate the # Client Connections for the Share Name of Users.

  4. If there are connected users, in the details pane, click View Connected Users.

  5. Right-click a user, and then click Disconnect.

Important

When you disconnect a user session, all sessions to all shares (not just the Users share) are closed.

To ensure the destination partition is formatted as NTFS

Verify that the partition (also referred to as a volume) or drive where you plan to move the Users Shared Folders is formatted as NTFS. This provides additional security and enables you to continue to use disk quotas on the Users Shared Folders.

  1. Click Start, point to Administrative Tools, and then click Computer Management.

  2. In the console tree, click Disk Management.

  3. In the details pane, verify that the File System for the destination partition is formatted as NTFS.

    If the partition is not formatted, you should format it as NTFS. To do so, right-click the free space, and then click New Logical Drive. Follow the instructions to complete the New Partition Wizard.

    If the partition is formatted as FAT or FAT32, you should convert the partition to NTFS. Converting the partition (rather than reformatting it) enables you to keep any existing data on the partition. For more information about converting a partition to NTFS, click Start, click Help and Support, and then search for “Reformatting or converting a partition to use NTFS.” The topic will be listed under the Help Topics section of Help and Support.

  4. Keep the Computer Management console open, and then continue to the next step.

To enable quotas on the destination partition

So that administrators can monitor and control the amount of disk space used by individual users, you must enable quotas on the destination partition.

Note

If you have other folders and files on the partition that you plan to move the Users Shared Folders, enabling quotas also affects those folders and files.

  1. Right-click the destination partition, and then click Properties.

  2. Click the Quota tab.

  3. Click Enable quota management, and then click Deny disk space to users exceeding quota limit.

  4. Select Limit disk space to, and then set it to 1 GB. For Set warning level to, use 900 MB.

  5. Select Log event when a user exceeds the quota limit, and Log event when a user exceeds their warning level. Click Apply.

  6. Click OK when you receive the message about enabling disk quotas.

  7. Leave the Computer Management console open, and then continue to the next step.

To export and import quota settings

You must export the quota settings from the source partition and then import the settings to the destination partition.

  1. In the console tree, click Disk Management.

  2. Right-click the source partition, and then click Properties.

  3. Click the Quota tab.

  4. Click Quota Entries.

  5. From the menu, click Edit, and then click Select all.

  6. From the menu, click Quota, and then click Export. Save the file as Original_quotas to the My Documents folder.

  7. Right-click the destination partition, and then click Properties.

  8. Click the Quota tab.

  9. Click Quota Entries.

  10. From the menu, click Quota, and then click Import. Select Original_quotas in the My Documents folder, and then click Open.

  11. When a message appears asking if you want to replace the existing entry for the BUILTIN\Administrators quota, click Yes.

To move the Users Shared Folders folder to the destination partition

Use the Xcopy command to copy the Users Shared Folders folder from the source partition to the destination partition. This method preserves the file ownership settings and discretionary access control list (DACL) information.

  1. Click Start, click Run, and then type Cmd.

  2. At a command prompt, type the following, where C is the source partition and D is the destination partition:

    Xcopy C:\Users Shared Folders D:\Users Shared Folders /e /o /d /h /v /c>>C:\Copyresults.txt
    

Note

For an explanation of each parameter, see the table at the end of the procedure.

  1. Press ENTER, and then the cursor will pause. Type D for Directory.

Note

When the output of the Xcopy command is redirected to a file, the following prompt is not displayed: Does D:\Users Shared Folders specify a file name or directory name on the target (F = file, D = directory)?. Although the prompt is not displayed, you must type D to complete the command.

  1. Using Windows Explorer, open C:\Copyresults.txt and verify if any errors occurred during the file copy. You can also compare the number and size of the files that were in the Users folder in the source partition with the number of files that are in the destination partition.

Note

You will delete the original Users Shared Folders in the next procedure, “To share the Users Shared Folders.”

Command Line Parameters   
Parameter Description

C

The original location of the Users Shared Folders. The default location is C:\Users Shared Folders, where C: is the root directory (the top-level folder or directory on a computer).

D

The partition on the disk where you plan to move the Users Shared Folders.

/e

Copies all subdirectories, even if they are empty.

/o

Copies file ownership and discretionary access control list (DACL) information.

/d

Copies only those files whose source time is newer than the destination time.

To copy files changed on or after a specified date, type /d: m-d-y, where m-d-y is the specified date, in month-day-year format, to begin checking for file changes.

/h

Copies files with hidden and system file attributes. By default, Xcopy does not copy hidden or system files.

/v

Verifies each new file.

/c

Ignores errors

>>C:\Copyresults.txt

Appends the results of the copy to a file named Copyresults.txt.

Note

For more information about Xcopy, type Xcopy /? at the command prompt.
An alternative to Xcopy is RoboCopy, which is available at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=20249).

To share the Users Shared Folders

You must share the Users Shared Folders on the destination partition so that users can access their individual data folders. The folder must be shared with the share name of Users or the folder will not be backed up by the Windows Small Business Server 2003 Backup Wizard. Additionally, if you share the folder as a name other than Users and have My Documents Redirection enabled, you will have to reconfigure the share name referenced by the redirection in the Client Document Redirection task.

  1. Click Start, and then click Server Management.

  2. In the console tree, click Shares.

  3. In the details pane, right-click Users, and then click Stop Sharing.

  4. Click Yes when the message appears asking if you are sure you want to stop sharing the folder.

  5. In the details pane, click Add a Shared Folder.

  6. In the Share a Folder Wizard, configure your server by using the information provided in Table 1:

Table 1 - Share a Folder Wizard

Wizard Page Action

Folder Path

Browse to the destination Users Shared Folders.

Name Description, and Settings

  1. For Share name, type Users.

    <ul>
    <li><strong>IMPORTANT</strong><br />
    <br />
    </li>
    <li>If you are using the Windows Small Business Server 2003 Backup Wizard, the Users Shared Folders will not be backed up if you change the share name from Users. Additionally, if you change the share name for the Users Shared Folders and have My Documents Redirections enabled, the My Documents Redirection will not work unless the Client Document Redirection task is run using the new share name.<br />
    <br />
    </li>
    </ul></li>
    <li>For <strong>Description</strong>, type <strong>Users Shared Folders.</strong><br />
    <br />
    </li>
    </ol></td>
    </tr>
    <tr class="odd">
    <td><p>Permissions</p></td>
    <td><ol>
    <li>Click <strong>Use custom share and folder permissions</strong>, and then click <strong>Customize</strong>. The Customize Permissions dialog box appears.<br />
    <br />
    </li>
    <li>With the <strong>Everyone</strong> group selected, click <strong>Remove</strong>.<br />
    <br />
    </li>
    <li>Click <strong>Add</strong>, and add the following groups with the specified permissions<br />
    <br />
    
    <ul>
    <li>Domain Admins, Full Control<br />
    <br />
    </li>
    <li>Domain Users, Full Control<br />
    <br />
    </li>
    <li>SBS folder Operators, Full Control<br />
    <br />
    </li>
    </ul></li>
    </ol></td>
    </tr>
    </tbody>
    
  1. Follow the instructions to complete the Share a Folder Wizard.

  2. After verifying that all folders and files were copied, you can delete the original Users Shared Folders. Using Windows Explorer (click Start, and then click Run, and then type Explorer), browse to and then delete C:\Users Shared Folders, where C is the drive letter for the source partition.

To enable file version retention

With file version retention enabled (this is also called Shadow Copies), users can revert to a version of a file that they accidentally deleted or overwrote that was saved to the user folder in the Users Shared Folders. To enable the file version retention, you can run the Backup Configuration Wizard and choose to enable the retention of file versions on the last page. Optionally, you can complete this task manually using Windows Explorer.

Using the Backup Configuration Wizard
  1. Click Start, and then click Server Management.

  2. In the console tree, click Backup.

  3. In the details pane, click Configure Backup. Follow the instructions to complete the Backup Configuration Wizard. On the Storage Allocation for Deleted Files and E-mail page, ensure that the option to Enable periodic snapshots of users’ shared folders is enabled.

Using Windows Explorer to manually enable shadow copies
  1. Using Windows Explorer, browse to the destination partition (drive letter) where the Users Shared Folders is located.

  2. Right-click the destination partition, and then click Properties.

  3. Click the Shadow Copies tab, and then click Enable.

  4. Click Yes to the message confirming that you want to enable shadow copies.

Step 4: Move the Windows SharePoint Services Databases

The Windows SharePoint Services databases use an instance of WMSDE. This is where the Company Web site documents are stored. Moving the databases requires the following steps:

  • Stopping the Internet Information Services (IIS) Web sites for Windows SharePoint Services

  • Verifying that the Windows SharePoint Services instance of WMSDE is running

  • Connecting to the Windows SharePoint Services instance of WMSDE and detaching the databases

  • Moving the Windows SharePoint Services databases to a new folder

  • Attaching the databases to the Windows SharePoint Services instance of WMSDE

  • Deleting the source Windows SharePoint Services databases

  • Starting the IIS Web sites for Windows SharePoint Services

  • Ensuring that the Windows SharePoint Services databases on the destination partition are excluded from anti-virus scans

To stop the Internet Information Services (IIS) Web sites for Windows SharePoint Services

To prevent users from accessing Windows SharePoint Services sites while you are moving the databases, stop the related IIS Web sites. If you have created additional Windows SharePoint Services sites, you should stop those Web sites as well.

  1. Click Start, click Server Management.

  2. Double-click Advanced Management, double-click Internet Information Services, double-click YourServer, and then double-click Web Sites.

  3. Right-click Microsoft SharePoint Administration, and then click Stop.

  4. Right-click SharePoint Central Administration, and then click Stop.

  5. Right-click Companyweb, and then click Stop.

To verify that the Windows SharePoint Services instance of WMSDE is running

Before moving the SharePoint instance of WMSDE, you should verify that the service for this instance is actually running. If the service is not running, you will not be able to complete any of the steps to move the database.

  1. Click Start, click Run, and then type Services.msc.

  2. Ensure that the Status of the MSSQL$SHAREPOINT service is listed as Started. If the service is not started, right-click the service, and then click Start.

To connect to the Windows SharePoint Services instance of WMSDE and detach the databases

Before moving the Windows SharePoint Services instance of WMSDE, you must connect to the instance and detach the two databases used by the instance.

  1. Click Start, click Run, and then type Cmd.

  2. Type the following command, considering the following bullet points, and then press ENTER.

    • The -E, -S, and -Q command line parameters must be typed as uppercase letters because they are case sensitive.

    • ServerName is the name of the computer running Windows Small Business Server 2003. To locate the ServerName, click Start, click Run, and then type Cmd. At the command prompt, type Set. It is listed as COMPUTERNAME.

    Osql -E -S ServerName\SharePoint -Q “sp_detach_db 'STS_Config'”
    

Important

If you receive the following error message, WMSDE might not be running or you might have provided an incorrect name for the named instance of WMSDE that is installed:

Important

[Shared Memory]SQL Server does not exist or access denied. [Shared Memory]ConnectionOpen (Connect()).

  1. Close the Server Management console. Wait one minute, and then repeat the command from Step 2 for the STS_ServerName_1 database, where ServerName is the name of the computer running Windows Small Business Server 2003.

    Osql -E -S ServerName\SharePoint -Q “sp_detach_db 'STS_ServerName_1'”
    

Note

The Server Management console maintains a connection to the databases so you must close the console or the command will fail.

To move the Windows SharePoint Services databases to a new folder

Create a folder for the databases on the destination partition, and then move the databases. You should use a partition formatted as NTFS. Otherwise, you will not be able to set the permissions for the database folders (Steps 3-7).

  1. Using Windows Explorer (click Start, click Run, and then type Explorer), create a folder on the destination partition named MSDEDatabases.

  2. Right-click the MSDEDatabases folder, and then click Properties.

  3. Click the Security tab.

  4. Click Advanced, and then clear the check box labeled Allow inheritable permissions from the parent to propagate to the object and all child objects. Include these with entries explicitly defined here.

  5. When prompted for what you want to do with the parent permission entries, click Remove.

  6. The permissions default to Administrators with Full Control.

Note

If you renamed the built-in Administrator account to a different account name, you must use that new account name.

  1. Using Windows Explorer, create a folder named SharePoint within the MSDEDatabases folder created in Step 2.

  2. Using Windows Explorer, copy the following files from the source database location (by default the location is C:\Program Files\Microsoft SQL Server\MSSQL$SharePoint\Data) to the folder created in Step 7:

    STS_Servername_1.mdf

    STS_Servername_1_Log.ldf

    STS_Config.mdf

    STS_Config_Log.ldf

To attach the databases to the Windows SharePoint Services instance of WMSDE

You must attach the databases you moved to the destination partition back to the Windows SharePoint Services instance of WMSDE.

  1. Click Start, click Run, and then type Cmd.

  2. Type the following command, considering the following bullet points, and then press ENTER.

    • The -E, -S, and -Q command line parameters must be typed as uppercase letters because they are case sensitive.

    • ServerName is the name of the computer running Windows Small Business Server 2003

    • D is the drive letter for the new location of the database.

    Osql -E -S ServerName\SharePoint -Q “sp_attach_db 'STS_Config', 'D:\MSDEDatabases\SharePoint\STS_Config.mdf', 'D:\MSDEDatabases\SharePoint\STS_Config_Log.ldf'”
    
  3. Repeat the command from Step 2 for the STS_ServerName_1 database, where ServerName is the name of the computer running Windows Small Business Server 2003.

    Osql -E -S ServerName\SharePoint -Q “sp_attach_db 'STS_ServerName_1', 'D:\MSDEDatabases\SharePoint\STS_ServerName_1.mdf', 'D:\MSDEDatabases\SharePoint\STS_ServerName_1_Log.ldf'”
    

To delete the source Windows SharePoint Services databases and log files

  • Using Windows Explorer, delete STS_Config.mdf, STS_Config_Log.ldf, STS_ServerName_1.mdf, and STS_ServerName_Log.ldf from the source partition. By default the location is C:\Program Files\Microsoft SQL Server\MSSQL$SharePoint\Data.

To start the Internet Information Services (IIS) Web sites for Windows SharePoint Services

  1. Click Start, click Server Management.

  2. Double-click Advanced Management, double-click Internet Information Services, double-click YourServer, and then double-click Web Sites.

  3. Right-click Microsoft SharePoint Administration, and then click Start.

  4. Right-click SharePoint Central Administration, and then click Start.

  5. Right-click Companyweb, and then click Start.

To ensure that the Windows SharePoint Services databases on the destination partition are excluded from anti-virus scans

  • After completing the move of the Windows SharePoint Services databases, you should remove the MSDEDatabases folder from the list of folders being scanned by anti-virus software running on your server. For more information about removing folders from an anti-virus scan, see your anti-virus manufacture’s documentation.

Step 5: Move the Monitoring Database

The Monitoring database uses an instance of MSDE 2000. This is where the information for the monitoring reports is stored. Moving the Monitoring instance of MSDE 2000 requires the following steps:

  • Verifying that the Monitoring instance of MSDE 2000 is running

  • Connecting to the Monitoring instance of MSDE 2000 and detaching the database

  • Moving the Monitoring database to a new folder

  • Attaching the databases to the Monitoring instance of MSDE 2000

  • Deleting the source Monitoring database and log file

  • Ensuring that the Monitoring database on the destination partition is excluded from anti-virus scans

To verify that the Monitoring instance of MSDE 2000 is running

Before moving the Monitoring instance of MSDE 2000, you should verify that the service for this instance is actually running. If the service is not running, you will not be able to complete any of the steps to move the database.

  1. Click Start, click Run, and then type Services.msc.

  2. Ensure that the Status for the MSSQL$SBSMONITORING service is listed as Started. If the service is not started, Monitoring might not be configured. If Monitoring is not configured, it is not necessary to move the database.

    To verify if monitoring is configured, click Start, and then click Server Management. In the console tree, click Monitoring and Reporting. If Monitoring is configured, the performance and usage reports are displayed in the details pane.

To connect to the Monitoring instance of MSDE 2000 and detach the database

Before moving the Monitoring instance of the MSDE 2000, you must connect to the instance and detach the database used by the instance.

  1. Click Start, click Run, and then type Cmd.

  2. Close the Server Management console. The Server Management console maintains a connection to the databases so you must close the console or the command will fail. Wait one minute, and then type the following command, considering the following bullet points, and then press ENTER.

    • The -E, -S, and -Q command line parameters must be typed as uppercase letters because they are case sensitive.

    • ServerName is the name of the computer running Windows Small Business Server 2003. To locate the ServerName, click Start, click Run, and then type Cmd. At the command prompt, type Set. It is listed as COMPUTERNAME.

    Osql -E -S ServerName\SBSMonitoring -Q “sp_detach_db 'SBSMonitoring'”
    

Important

If you receive the following error message, MSDE 2000 might not be running or you might have provided an incorrect name for the named instance of MSDE 2000 that is installed:

Important

[Shared Memory]SQL Server does not exist or access denied. [Shared Memory]ConnectionOpen (Connect()).

To move the Monitoring database to a new folder

If you did not move the Windows SharePoint Services instance of WMSDE, you must first create a folder for the database on the destination partition before moving the databases. You will then create a folder for the Monitoring database and copy the relevant files.

  1. If you did not choose to move the Windows SharePoint Services instance of WMSDE, you will need to first create the MSDEDatabases folder and assign the appropriate permissions. To do so, see the procedure “To move the Windows SharePoint Services instance of WMSDE” in the previous section.

  2. Using Windows Explorer, create a folder named Monitoring within the MSDEDatabases folder created in the previous step.

  3. Using Windows Explorer, copy the following files from the original database location (by default the location is C:\Program Files\Microsoft SQL Server\MSSQL$SBSMonitoring\Data) to the Monitoring folder created in Step 2:

    SBSMonitoring.mdf

    SBSMonitoring_Log.ldf

To attach the database to the Monitoring instance of MSDE 2000

You must attach the database you moved to the destination partition back to the Monitoring instance of MSDE 2000.

  1. Click Start, click Run, and then type Cmd.

  2. Type the following command, considering the following bullet points, and then press ENTER.

    • The -E, -S, and -Q command line parameters must be typed as uppercase letters because they are case sensitive.

    • ServerName is the name of the computer running Windows Small Business Server 2003

    • D is the drive letter for the new location of the database.

    Osql -E -S ServerName\SBSMonitoring -Q “sp_attach_db ‘SBSMonitoring', 'D:\MSDEDatabases\Monitoring\SBSMonitoring.mdf', 'D:\MSDEDatabases\Monitoring\SBSMonitoring_Log.ldf'”
    

To delete the source Monitoring database and log file

  • Using Windows Explorer, delete SBSMonitoring.mdf and SBSMonitoring_Log.ldf from the original location. By default the location is C:\Program Files\Microsoft SQL Server\MSSQL$SBSMonitoring\Data.

To ensure that the Monitoring database on the destination partition is excluded from anti-virus scans

  • After completing the move of the Monitoring database, you should remove the MSDEDatabases folder from being scanned by anti-virus software running on your server. For more information about removing folders from an anti-virus scan, see your anti-virus manufacture’s documentation.

Step 6: Move Exchange Databases and Log Files

There are two Exchange databases, the mailbox store and public folder store, where users' mailboxes and folders are stored. The transaction log files for the Exchange database are stored in the log files. To move the Exchange databases and log files, you need to follow the Knowledge Base article referenced in the procedure. Moving the Exchange databases and log files requires the following steps:

  • Moving Exchange Databases and Log files by following the reference Knowledge Base article

  • Ensuring that Exchange databases on the destination partition are excluded from anti-virus scans

To move Exchange databases and log files

To ensure that Exchange databases on the destination partition are excluded from anti-virus scans

  • After completing the move of the Exchange databases, you should remove the destination folder from being scanned by anti-virus software running on your server. For more information about removing folders from an anti-virus scan, see your anti-virus manufacture’s documentation.

Step 7: Move the Sent Faxes Folder

The Sent Faxes folder is where outgoing faxes are archived. To move the Sent Faxes folder, you will change the location where sent faxes are archived, and then copy the existing sent faxes to the destination location.

To change the location where Sent Faxes are archived

  1. Click Start, and then click Server Management.

  2. In the console pane, right-click Fax, and then click Properties.

  3. Click the Sent Items tab.

  4. Under Archive folder, type D**:\SentFaxes**, where D is the letter of the destination partition and SentFaxes is the name of the folder where sent faxes will be archived.

  5. Click Apply.

  6. When prompted for if you want to create a new folder with the access permissions for Fax Server, click Yes.

To move the existing archived Sent Faxes

You can copy the existing archived faxes to the new location, and then delete the source folder. The default location for the Sent Faxes folder is C**:\Fax\Archive**.

  1. Click Start, click Run, and then type Cmd.

  2. At a command prompt, type the following, where C is the source partition and D is the destination partition:

    Xcopy C:\Fax\Archive D:\SentFaxes /e /o /d /h /v /c>>C:\Copyresults2.txt
    

Note

For an explanation of each parameter, see the table in the procedure “To move Users Shared Folders to destination partition.”

  1. Press ENTER, and then the cursor will pause. Type D for Directory.

Note

When the output of the Xcopy command is redirected to a file, the following prompt is not displayed: Does D:\Users Shared Folders specify a file name or directory name on the target (F = file, D = directory)?. Although the prompt is not displayed, you must type D to complete the command.

  1. Using Windows Explorer, open C:\Copyresults.txt and verify if any errors occurred during the file copy. You can also compare the number and size of the files that were in the Fax folder in the source partition with the number of files that are in the destination partition.

To delete the Sent Faxes folder

  • Using Windows Explorer, delete the source Sent Faxes folder. By default the location is C**:\Fax\Archive**.

Step 8: Move the ClientApps Shared Folder

By default, the ClientApps shared folder takes up approximately 1 GB of space. However, if you have added several applications to this folder that you are deploying using the Assign Applications Wizard, the folder might have grown considerably in size. In this case, you might want to move the ClientApps shared folder to another location. Alternately, you can create a new shared folder just for applications that you want to deploy.

To move ClientApps shared folder

Step 9: Move the Windows Server Update Services Folder

Updates are divided into two parts: a metadata part that describes the update, and the files required to install the update on a computer. Although metadata that describes updates is stored in the Windows Server Update Services (WSUS) database, the update files that are used to install the updates are stored in a folder on the server. You will use the Wsusutil.exe command to move the update files to a different location.

To move the WSUS update folder

Wsusutil.exe is included when you install WSUS and is located in the Updates Services\Tools folder.

  1. Click Start, click Run, and then type Cmd.

  2. Type the following command, and then press ENTER.

    cd %drive%\Program Files\Update Services\Tools
    
  3. Type the following command, and then press ENTER.

    wsusutil movecontent DestinationPath LogFile
    

    DestinationPath is the path where you want to copy the update files. The path must exist. LogFile is the path and filename of the log file to create.

Step 10: Complete the Process

After moving the data folders, you should notify users that the resources are again available for use. Additionally, you should complete a full backup.

To notify users that the resources are again available for use

  • If you moved the data folders while users were still connected to the network, you should inform the users that the resources are now available for use.

To complete a full backup

For the latest information about Windows Small Business Server 2003, see the Windows Small Business Server 2003 Web site (https://go.microsoft.com/fwlink/?LinkId=22341).