Bellingham IT Services

Complete the following steps to move the SharePoint Services content database.

1. To avoid user access to the internal Web site while you are moving data, stop the internal Web site. In the Windows SBS Console, click the Shared Folders and Web Sites tab, click Web sites, and then click Disable this site.

2. Use the Windows SharePoint Services 3.0 tools to remove the content database from the Web application. Removing the content database does not delete it—it only removes the association of the database with the Web application. This action is analogous to detaching a database in SQL Server because the content of the database remains intact.

   1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

   2. In the User Account Control prompt, click Continue.

   3. In the Central Administration page, click the Application Management tab.

   4. In the SharePoint Web Application Management section, click Content databases.

   5. On the Manage Content Databases page, click the content database that you want to move (ShareWebDB).

   6. On the Manage Content Database Settings page, in the Remove Content Database section, select Remove content database, and then click OK.

Copy or move the ShareWebDb.mdf and ShareWebDb_log.ldf files from %COMMPROGRAMFILES%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\ to a destination folder.

Note
The content database files should be stored on the same server where you installed SQL Server.

1. If you installed SQL Server 2005:

   Log on to the server where you want to install SQL Server to use as the content database.

2. Install SQL Server 2005 or SQL Server 2008.

3. If you install SQL Server on a separate server from the server running Windows SBS 2008, you must configure it to allow remote connections.

   1. Enable remote connections on the SQL Server that you want to connect to from a remote computer.

   2. Turn on the SQL Server Browser Service.

   3. Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser Service.

      For more information, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125442.

4. If you installed SQL Server 2008:

   1. Start the SQL Configuration Manager, browse to the SQL Server Network Configuration node, and then select SQL Server.

   2. In the right pane, right-click TCP/IP, and then click Enable.

   3. Restart the SQL Browser Service.

   4. To configure services such as Start, Stop, Pause, Restart, and Update service accounts, do the following:

      1. Start the SQL Configuration Manager, browse to SQL Server Services, and then select SQL Server.

      2. In the right pane, right-click the service that you want to change, and then click the appropriate option.

      3. To change the service account, right-click the service, click Properties, and then click the Log On tab.

1. If the destination SQL Server instance is on the Windows SBS 2008 server on which the Windows SharePoint Services installed, you can use the SharePoint 3.0 Central Administrator to add the new content database.

   1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administrator.

   2. On the Application Management page, in the SharePoint Web Application Management section, click Content databases.

   3. On the Manage Content Databases page, click Add a content database.

   4. On the Add Content Database page, in the Database Server section, type the exact name of the database instance.

   5. In the Database Name section, type the exact name of the transferred content database (ShareWebDb), and then click OK.

After you move the content database to SQL Server, you are no longer able to use the Move Windows SharePoint Services Data task from the Windows SBS Console (Server Storage, which is located on the Backup and Server Storage tab). This is because the task can only move data for the Windows internal database.

If the disk where you are hosting the content database is running out of disk space, you can move the data by using the Detach and Attach components.

For more information about how to do this in SQL Server 2008, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125443.

For more information about how to do this in SQL Server 2005, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125445.

After you move the content database to SQL Server, you can continue to move it to other SQL Server instances as needed. For more information, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125446.

Scripts to Mass Create Users and Email for POC or Test Environments

During a recent Exchange migration in the Proof of Concept phase I was looking for a way to quickly generate a large number of users with email in their accounts to test through steps of the migration (and document for their environment). To speed up the process for creating these accounts and email I created the attached scripts. Please note: These scripts are NOT production level scripts and should NOT be used in a production environment. They are designed for testing or proof of concept environments only. I have used them in two Active Directory 2003 environments with a large amount of success.

So, with those caveats in place here’s how they work!

§       First, Backup your environment (ok, one last caveat in case)

§       Next create each of the scripts in this blog entry with the names specified at the top and put them into the C:\ directory on the server which hosts the Exchange services in the POC.

§       Once they are created there are four steps involved in creating the users.

1)     Create the MigrationTest top level OU within the domain

2)     Run the script to create the users (createusers.bat)

3)     In AD Users and Computers enable and create mailboxes for the users (highlight all users in the MigrationTest OU at the same time to enable them and create their mailboxes)

4)     Run the script to create the mail (createmassmail.bat)

CreateEmail.bat

@echo off
rem General: Make sure that the new accounts are enabled and have mailboxes before running this
rem Usage: script (# of emails to send) (originating email) (receiving email)
rem Example: createmail 50 administrator@abc.domainname.com TestUser@abc.domainname.com (creates 50 emails from the logged in account to TestUser@abc.domainname.com)

if %1%x==x goto Params
if %2%x==x goto Params
if %3%x==x goto Params

set /a n=%1
set /a i=0
set /a sp=" "
:loop
set /a i+=1
 echo call createoneemail %2% %%sp% %3% %%sp% %i%
 call createoneemail %2% %%sp% %3% %%sp% %i%
 if %1x==%i%x goto end
goto loop
:Params
echo Please use the syntax: script #email sender receiver
echo Example: createmail 50 administrator@abc.domainname.com TestUser@abc.domainname.com
goto exit

:end
echo Email should have been sent!.
echo

:exit

CreateMassMail.bat

@echo off
rem General: Make sure that the new accounts are enabled and have mailboxes before running this
rem Usage: script (# of users created) (naming for users) (domain)
rem Example: createmail 50 TestUser @abc.domainname.com (sends 1000 emails to each of the 50 TestUser accounts)

if %1%x==x goto Params
if %2%x==x goto Params
if %3%x==x goto Params

set /a nn=%1
set /a ii=0
set /a sp=" "
:loop
set /a ii+=1
 echo call createmail 100 administrator%3% %%sp% %2% %%ii%%3%
 call createmail 100 administrator%3% %%sp% %2% %%ii%%3%
 if %1x==%ii%x goto end
goto loop
:Params
echo Usage: script (# of users created) (naming for users) (domain)
echo Example: createmail 50 TestUser @abc.domainname.com (sends 1000 emails to each of the 50 TestUser accounts)

goto exit

:end
:exitCreateOneEmail.bat

dim ArgObj, var1, var2
Set ArgObj=WScript.Arguments
' Parameters = (originating mailbox) (receiving mailbox) (number)
var1=ArgObj(0)
var2=ArgObj(1)
var3=ArgObj(2)

set objEmail = CreateObject("CDO.Message")
objEmail.From = var1
objEmail.To = var2
objEmail.Subject = "Testing Email number " & Var3
objEmail.Textbody = "Testing Email message body."
objEmail.Send

'Clear object out of memory
set ArgObj=Nothing

CreateOneUser.bat

del /f c:\importuser.ldf
echo dn: CN=%1,OU=MigrationTest,DC=%5,DC=%4,DC=%3>> %2
echo changetype: add>> %2
echo objectClass: top>> %2
echo objectClass: person>> %2
echo objectClass: organizationalPerson>> %2
echo objectClass: user>> %2
echo cn: %1>> %2
echo givenName: %1>> %2
echo sAMAccountName: %1>> %2
ldifde -i -k -f %2 -s %computername% -j c:\

CreateUsers.bat

@echo off
rem General: Create an OU called MigrationTest in this domain before running the script
rem Usage: script (# of users to create) (naming for users) (reversed version of DC=abc,DC=domainname,DC=com)
rem Example: createusers 50 TestUser com domainname abc (creates 50 users named TestUser1-50 in the
rem abc.domainname.com domain.

if %1%x==x goto Params
if %2%x==x goto Params
if %3%x==x goto Params
if %4%x==x goto Params

set /a n=%1
set /a i=0
set /a sp=" "
:loop
set /a i+=1
 echo Creating %2% %%i%
 echo call createoneuser %2% %%i% c:\importuser.ldf %3% %%sp% %4% %%sp% %5%
 call createoneuser %2% %%i% c:\importuser.ldf %3% %%sp% %4% %%sp% %5%
 if %1x==%i%x goto end
goto loop
:Params
echo Please use the syntax: script #users naming dc1 dc2 dc3
echo Example: createusers.bat 50 TestUser com domainname abc
echo The last three are the reversed version of DC=abc,DC=domainname,DC=com
:end
echo Users created will need to be enabled and have mailboxes enabled for them.
echo

ReadMe.Txt

The purpose of these scripts is to create testing mailboxes and mail within the mailboxes to assist with POC testing of Exchange migrations.

The scripts in this folder are designed to be copied to the C:\ directory on the server which hosts the Exchange services.

There are four steps involved in the process:

1) Create the MigrationTest top level OU within the domain
2) Run the script to create the users (createusers.bat)
3) In AD Users and Computers enable and create mailboxes for the users
4) Run the script to create the mail (createmassmail.bat)

Details:

1) AD Users and Computers, new OU called MigrationTest
2) createusers.bat (# of users) (naming) (reversed domain name)
example: createusers.bat 450 TestUser com domainname abc
(creates 450 users with TestUser# in the abc.domainname.com domain)
3) AD users and computers, open the MigrationTest OU highlight all users, right-click and enable account. Then right-click and under Exchange tasks create the mailbox.
4) createmassmail.bat (# of users) (naming) (email extension)
example: createmassmail.bat 450 TestUser @abc.domainname.com
(creates 100 email messages from administrator to each of the 450 TestUser users)

Known issues:

This was built upon a three level domain name (abc.domainname.com), if it is a two or four level the createoneuser.bat file will need the second line of the file changed to reflect
the change. It's currently:

echo dn: CN=%1,OU=MigrationTest,DC=%5,DC=%4,DC=%3>> %2

Changed to a two level domain:

echo dn: CN=%1,OU=MigrationTest,DC=%4,DC=%3>> %2

Will work for a two level domain (xyz.com as an example).

Let me know if you find these to be useful!