How to implement SharePoint 2010 Access Services

Introduction

BI Services Series

How to implement SharePoint 2010 Access Services

How to setup Secure Store and BCS to access LOB data

How to enable document conversion from Word to HTML in SharePoint 2010

How to set up Excel Services to use Secure Store Services and an unattended service account

This posting walks through the process of implementing SharePoint 2010 Access Services, step-by-step.  Implementing Access services requires that the administrator work with several different technologies, including Silverlight, Session State, SharePoint Services and Service Applications, and Microsoft Office products.  Implementing Access services will involve several key steps:

1. Install Silverlight: Microsoft Silverlight us used to generate many of the Access Online user interfaces, such as New and Edit forms.
2. Enable ASP.NET Session State Service: SharePoint Server 2010 uses ASP.NET session state to persist user data between successive requests.  It is needed when working with online implementations of Microsoft Access, Excel and other office tools.
3. Configure Access services: configure service applications.

This posting was developed on the small farm, two-tier SharePoint Server 2010 environment developed in a previous posting.

Step 1: Install Silverlight on clients

• Install Microsoft Silverlight on all client machines that will be connecting to the online Access database application.

Step 2: Enable ASP.NET Session State Service

1. In Central Administration, go: Application Management > Service Applications > Manage service applications.
2. Verify that the SharePoint Server ASP.NET Session State Service is not listed.
3. On the SharePoint Server 2010 host machine, open the SharePoint 2010 Management Shell.
4. Execute the following command:
• Enable-SPSessionStateService –DefaultProvision
  
5. In Windows Explorer, navigate to the Web.Config file of the web application that will be used to host Access webs:
• C:\Inetpub\wwwroot\wss\VirtualDirectories\
  
6. Edit the Web.Config file by setting enableSessionState to True.
   
7. Save the file.
• Changes to the web application Web.Config file automatically trigger a restart of the application.
8. To manually restart IIS, use iisreset:
   
9. In Central Administration, go: Application Management > Service Applications > Manage service applications.
10. Verify that the SharePoint Server ASP.NET Session State Service is now listed
    
    NOTE: failure to enable ASP.NET Session State Service will not stop Microsoft Access database applications from being successfully published to SharePoint Server 2010.  However, when you attempt to actually connect to the web-enabled version, you may experience the following error:
    
    If this error does occur, check to make sure that the ASP.NET Session State Service has been started.

Step 3: Configure Access Services

1. Install Reporting Services Add-In:
1. Logon to the SharePoint Server 2010 host.
2. Install the SQL Microsoft SQL Server 2008 R2 Reporting Services Add-in for SharePoint 2010
   
2. Provision Service Account:
• Use sp_app domain account.
3. Register service account as a managed account:
1. In Central Administration, go: Security > General Security > Configure managed accounts.
2. Add domain service account to list of managed accounts
   
4. Start Access Services:
1. In Central Administration, go: Application Management > Manage services on server.
2. Look for Access Database Service in the list
   
3. Click Start if the service is not already started.
• In a default small farm two-tier installation, this service will already have been started.
5. Create Access Service Application
1. In Central Administration, go: Application Management > Manage Service Applications.
2. Look for Access Services in the list
   
3. Create a new Access Service Application if one is not already created.
• In a default small farm two-tier installation, this service application will already have been created.

Optional: Publish the Northwind Traders sample Access application

1. Download the Northwind sample template, Northwind.accdt, for Office 2010. 
2. Double-click the template to create the runnable database application, Database.accdb.
3. Change the filename to Northwind.accdb, and the save.  The application will open and prompt you to login
   
4. On the ribbon, click the File tab, select Save and Publish, and then select Publish to Access Services:
   
5. Click the Run Compatibility Checker.
6. View the Compatibility Checker results
   
7. Enter the Server URL and enter a custom name for the new site that will be created for this Access application.
8. Click Publish to Access Services.  Logon when requested.
9. After a minute or two, a success prompt appears
   
10. Click the URL to view the online application.  After a minute, a browser will open to the site
    
11. This completes the test.

Optional: Remove a published Access database application

1. From the Access database view:
1. At the top of the online Access database view, click Options, and then click Settings.
2. In the Settings group of links, click Delete this Site.
2. From the site's Site Settings:
1. In the browser address bar, modify the URL by appending, "_layouts/settings.aspx" to the URL:
• ...[server]/[Access database site]/_layouts/settings.aspx
2. In the Site Actions group, click Delete this site.
3. From the root site:
1. Navigate to the root site.
2. From Site Actions, click Site Settings.
3. In the Site Administration group, click Sites and Workspaces.
4. In the list of Sites, click the "X" associated with the site you want to delete.

Summary

This posting has presented a walkthrough for implementing SharePoint Server 2010 Access Services.  For additional detail on the steps and procedure presented here, see the References below.

References

• Microsoft MSDN Blogs: Using Session State in SharePoint 2010
• MSDN Developer Network: Session State Management in SharePoint
• Microsoft TechNet: Manage the State Service (SharePoint Server 2010)
• MSDN Developer Network: Working with Web.config Files
• MSDN Developer Network: Editing ASP.NET Configuration Files
• MSDN Developer network: Managing Changes to Configuration Settings
• TechNet: Set up and configure Access Services (SharePoint Server 2010)
• Microsoft Download Center: Microsoft® SQL Server® 2008 R2 Reporting Services Add-in for Microsoft SharePoint® Technologies 2010
• Microsoft Office 2010: Build and publish an Access database to SharePoint
• Microsoft Office: Sample Access databases that you can download and adapt
• Microsoft Office: Northwind sales web database
• Microsoft Office: Desktop sales pipeline
• Institute for Informatics Georg-August-Universität Gottingen: The MONDIAL Database
• What About SharePoint: Set up and configure Access Services (SharePoint Server 2010)
• Nick Patel: Access Services in SharePoint 2010 - All You Need to Know
• Microsoft Developer Network: Creating Web Databases with Access 2010 and Access Services

Notes

• If you experience the error,  Specified method is not supported, when attempting to delete the published site, see this posting.

Error: Specified method is not supported

Problem

You attempted to delete a Microsoft Access database application from a SharePoint Server 2010 site, but experienced the following error:

Discussion

This error may occur after installing a service pack or cumulative update.

Solution

Run the SharePoint 2010 Products Configuration Wizard.

References

• SharePoint TechCenter Blog: Please Help: Correlation ID - Specified method is not supported
• JonTheNerd: SharePoint 2010: Unable to delete site/web after SP1

How to setup SharePoint 2010 user profile synchronization and MySites

Introduction

This posting presents a detailed, step-by-step walkthrough for setting up user profile synchronization and MySites in a SharePoint Server 2010 farm. It is based upon the small two-tier SharePoint Server 2010 farm created in a previous posting.  To prepare for this posting, Active Directory was populated with the Northwind Traders list of employees/users (9).  A new organizational unit was added to Active Directory, SharePoint Users, and the Northwind Traders users were added to this OU.  The synchronization that will be setup here is read only (from Active Directory to SharePoint Server).  Setting up synchronization and My Sites involves the following steps:

1. Provisioning accounts
2. Creating a new web application
3. Creating a new site collection
4. Provisioning a new profile service application
5. Configuring a new profile service connection
6. Testing

For additional information on any step, consult the references.

Step 1: Provision accounts

1. Provision existing SharePoint farm administration account (sp_admin):
1. Logon to the SharePoint Server host machine.
2. In Server Manager, go to: Configuration > Local Users and Groups > Groups.
3. Double-click the Administrators group
   
4. On the Administrators Properties dialog, click Add.
5. In the Select Users, Computers, Service Accounts, or Groups dialog, enter the SharePoint farm administration account.
6. Click Check Names:
   
7. Click OK.
8. On the Administrators Properties dialog, click OK.
9. Close Server Manager.
10. Go: Start > Administrative Tools > Local Security Policy.
11. On the Local Security Policy dialog navigation pane at left, go to: Security Settings > Local Policies > User Rights Assignment.
12. In the list pane at right, look for Allow log on locally.
    
13. Double-click Allow log on locally.
14. On the Allow log on locally Properties dialog, click Add User or Group.
15. In the Select Users, Computers, Service Accounts, or Groups dialog, enter the SharePoint farm administration account sp_admin.
• The SharePoint farm administration account must have local administrator privileges during this process - but only during this process.  Once you have successfully created profile synchronization and MySites, you can safely remove this local permission.
16. Click Check Names, and then click OK.
    
17. On the Allow log on locally Properties dialog, click OK.
18. Close the Local Security Policy applet.
19. Logout of the SharePoint Server host machine.
20. This concludes provisioning of the SharePoint farm administration account.
2. Create new SharePoint profile synchronization account:
1. Logon to the domain controller host.
2. Go: Start > Administrative Tools > Active Directory Users and Computers.
3. On the Active Directory Users and Computers dialog navigation pane at left, go to: Active Directory Users and Computers > [your domain] > Users.
4. From the Action menu, point to New and then select User.
5. Launch the Active Directory Users and Computers applet.
6. Enter information and name the account sp_sync.
7. Click Next, and then enter password.
8. Click Next, and then click Finish.
3. Provision new SharePoint profile synchronization account:
1. On the navigation pane at left, select the domain (contoso.com).
2. From the Action menu, select Delegate Control.
   
3. Click Next.
4. On the Users or Groups page of the Delegation of Control Wizard, click Add.
5. In the Select Users, Computers, or Groups dialog, enter the SharePoint farm administration account.
6. Click Check Names, and then click OK.
   
7. On the Users or Groups page of the Delegation of Control Wizard, click Next.
8. On the Tasks to Delegate page of the Delegation of Control Wizard, select the Create a custom task to delegate option, and then click Next.
9. On the Active Directory Object Type page of the Delegation of Control Wizard, click Next.
10. On the Permissions page of the Delegation of Control Wizard, enable General.
11. Scroll the Permissions list for the Replicating Directory Changes item, and then enable this item
    
12. Click Next, and then click Finish.
13. Close Active Directory Users and Computers.
14. Logout of the domain controller host (spdev11).
15. Logon to the SharePoint Server host (spdev12).
16. Launch Central Administration.
17. In the Quick Launch navigation pane at left, click Security.
18. At right, in the General Security group of links, look for Configure managed accounts:
    
19. Click Configure managed accounts.
20. On the Managed Accounts page, click Register Managed Account.
    
21. On the Register Managed Account page, in the Service account credentials section, enter the new account information (e.g., contoso\sp_sync).
22. Click OK.
23. In Central Administration, return to the main page.
24. This concludes provisioning of the SharePoint user profile synchronization account.

Step 2: Create new MySites web application

1. On the Central Administration Quick Launch pane at left, click Application Management.
2. On the Application Management page, in the Web Applications group of links, click Manage web applications.
3. On the Web Applications ribbon, look for the New button:
   
4. Click the New button.
5. Provision the new web application as follows:
1. Authentication: classic.
2. IIS Web Site: Create a new IIS web site: MySites (4200).
3. Port: 4200.
4. Application Pool: Create new application pool: MySites (4200) App Pool.
5. Security account: contoso\sp_sync.
6. Database Server: spdev11.
7. Database Name: WSS_Content_MySites.
   
8. Database Authentication: Windows authentication.
9. Service Application Connections:
• User Profile
• Manage Metadata
• Search
• Web Analytics
• Usage and Health data collection
  
10. Click OK.
11. In Central Administration, navigate back to the main page.
6. This concludes creating the new MySites web application.

Step 3: Create new MySites site collection

1. In Central Administration, on the Quick Launch navigation panel at left, click Application Management.
   
2. On the Application Management page, in the Site Collections group, click Create site collections.
3. Provision the site collection as follows:
1. From the Web Application dropdown, select the web application created in the previous step.
2. Title: enter a title.
3. In Select a template, click Enterprise, and then select My Site Host.
   
4. For the Primary Site Collection Administrator: enter the domain administrator account.
5. For the Secondary Site Collection Administrator: enter your domain admin account.
6. Click OK.
7. Click OK again.
4. In Central Administration, navigate back to the main page.
5. This concludes creating the new site collection.

Step 4: Provision new user profile service application

1. In Central Administration, on the Quick Launch navigation panel at left, click Application Management.
2. On the Application Management page, in the Service Applications group, click Manage service applications:
   
3. On the Service Applications ribbon, click the New button, and then select User Profile Service Application from the dropdown:
   
4. On the Create New User profile Service Application dialog, configure as follows (only non-default values shown here):
1. Name: User Profile Service App I.
2. Application Pool: Create new application pool.
3. Application pool name: User Profile Service App I.
4. Select a security account for this application pool: Configurable: Contoso\sp_sync
   
5. My Site Host URL: [site collection url].
6. Site Naming Format: User name (do not resolve conflicts).
7. Click OK.
8. On the Service Applications page, scroll down to see the newly created User Profile Service App I:
   
5. Open a command prompt.
6. Execute the following command:
• iisreset /noforce:
  
7. Once completed, close the command window.
8. Go: Start > Administrative Tools > Services.
9. Verify that the two Forefront Identity Manager services have been added and are started:
   
10. This concludes provisioning a new user profile service application.

Step 5: Configure synchronization connection

1. In Central Administration, on the Quick Launch navigation panel at left, click Application Management.
2. On the Application Management page, in the Service Applications group, click Manage service applications.
3. On the Service Applications page, scroll down the list of service applications and look for User Profile Service App I:
   
4. Select this service (don't click on its name, just the row).
5. On the Service Applications ribbon, click Manage.
6. On the User Profile Service App I page, look for the Synchronization group of links, and then click Configure Synchronization Connections.
7. On the Synchronization Connections page, click Create New Connection.
8. On the Add new synchronization connection page, configure as follows (only non-default values shown here):
1. Connection Name: User Profile Service App I Sync Connection.
2. Forest name: contoso.com.
3. Account name: contoso\sp_sync.
4. Password: [password]
   
9. Scroll down to the Containers section.
10. Click Populate Containers.
11. Select the users or organizational unit desired
    
12. Click OK..
13. In Central Administration, on the Quick Launch navigation panel at left, click Application Management.
14. On the Application Management page, in the Service Applications group, click Manage service applications.
15. On the Service Applications page, scroll down the list of service applications and look for User Profile Service App I
    
16. Click this link.
17. On the User Profile Service App I page, look for the Synchronization group of links, and then click Start Profile Synchronization
    
18. On the Start Profile Synchronization page, select Start Full Synchronization, and then click OK.
19. Wait. This will take several minutes or more.  Once completed, proceed to the next step.
20. Logout of Central Administration and close all browser instances.

Step 6: Test

1. Open a  browser and connect to the site.
2. Sign in as: Andrew.Fuller (Northwind Traders account).
3. After signing in, look for the user name in the upper right-hand corner, and click it.  A dropdown menu will appear:
   
4. Wait.
5. At the logon prompt, enter this user's username and password.
6. Wait. On first time connection, the new site must be created and provisioned. After a minute or so, the user's personal site will be displayed:
   
7. Close the web page.

Summary

This posting has presented a step-by-step walkthrough for setting up user profile synchronization and My Sites.  The synchronization here is read only (from Active Directory to SharePoint Server).  Additional work remains to add/remove/revise the fields to be imported from AD.

References

• Als Tech Tips:
• AlsTechTips: How to build and deploy clone servers on VMware Workstation
• AlsTechTips: Build a SharePoint Server 2010 Two-Tier Dev Environment on Windows 2008 R2
• TechNet Library:
• Create a New Organizational Unit
• Plan for profile synchronization (SharePoint Server 2010)
• Directory Domain Services permissions for profile synchronization (SharePoint Server 2010)
• Best practices for My Sites (SharePoint Server 2010)
• Plan for My Sites (SharePoint Server 2010)
• Configure profile synchronization (SharePoint Server 2010)
• IIS Reset Activity
• ADSI Edit (adsiedit.msc)
• Microsoft Download Center:
• User profile properties and profile synchronization planning worksheets for SharePoint Server 2010
• User Blogs:
• SharePoint Diary: Configuring My Sites & User Profile Synchronization in SharePoint 2010 - Step by Step
• Harbar: Rational Guide to implementing SharePoint Server 2010 User Profile Synchronization
• Where to find the FIM Client (miisclient.exe)
• MSDN Blogs:
• MSDN Blogs: Windows 2008 AND IISRESET.EXE

Notes

• Step 2: this posting follows best practices by isolating user mysites in a separate web application. OOTB, a User Profile Service Application service is already entered into the list of services.  However, this one is configured to create My Sites in a subsite off the main site.
• Step 5: the synchronization presented here is one-way: user profile information in Active Directory is harvested and then ingested into SharePoint Server; there is no write-back of this information to Active Directory after a user changes it.
• Synchronization Service Manager: tool useful for troubleshooting the SharePoint User Profile Service Application.  You'll find it at this folder location:

  \Program Files\Microsoft Office Servers\15.0\Synchronization Service\UIShell

  Look for miisclient.exe.  It enables you to view the real-time status of UPA processes, among many other things.  I don't use it to manage FIM; just to view status information.  For example, I have used to troubleshoot a UPA that failed to start.  As I tried different troubleshooting steps, I monitored Synchronization Service Manager, watching in real-time to see how far UPA started, before stopping.  It also provides helpful other information, such as confirmation of the Domain Controller that it is connecting to.  If you configured UPA using Auto Detect for DC, you can now determine exactly which DC it is connecting to.  You can also get confirmation of the service account that is running UPA (eg, the farm service account), and the number.

Build a SharePoint 2007 Two-Tier Farm on Windows 2003

Introduction

This posting walks through the process of building a small two-tier SharePoint Server 2007 farm on Windows Server 2003 R2 that can be used for testing and development.  Performed on VMware Workstation 7.X.  Components of this environment will include:

• Windows Server 2003 R2 Enterprise (trial version)
• SharePoint Server 2007
• SQL Server Express version 2005
• .NET Frameworks 2.0 and 3.0
• Domain controller
• DNS server

Building the environment involves the following discrete steps:

1. Build servers
2. Configure DC and DNS
3. Join Domain
4. Install SQL Server Express
5. Install SharePoint Server 2007

Step 1: Build Servers

• Build two Windows Server 2003 R2 Enterprise instances using the clone developed in a previous posting.
• Launch first server:
• during mini-setup, set name to spdev21.
• Launch second server:
• During mini-setup, set name to spdev23.

Step 2: Configure DC and DNS

• On the first server (spdev21):
1. On Manage Your Server, click Add or remove a role.  The Configure Your Server wizard is launched.
2. Configure domain as AdventureWorks.Com.
3. After completion, verify that new forward lookup, pointing to this DNS, was automatically created.
4. Reboot (automatic).
5. Verify Internet connectivity and access.
6. From Administrative Tools, launch Active Directory Users and Computers.
7. Add SharePoint service accounts: sp_admin, sp_web and sp_app.

Step 3: Join Domain

• On the second server (spdev23):
1. Configure network adaptor IP and DNS.
2. Verify Internet connectivity and access.

Step 4: Install SQL Server Express

1. On spdev21:
1. Install .NET Framework 2.0 SP2.
2. Install SQL Server Express (2005).
3. Add account sp_admin:
• Add roles: dbcreator, securityadmin.
4. Add own account as sysadmin.
5. Note the SQL Server instance name: SPDEV21\SQLEXPRESS.

Step 5: Install SharePoint Server 2007

1. Install .NET Framework 2.0.
2. Install .NET Framework 2.0 SP2.
3. Install .NET Framework 3.0.
4. Open a command window and navigate to: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727.
5. Run this command:
• aspnet_regiis -I
6. Verify that the SQL Server Browser service is running.  If it isn't, start it.
7. Perform an installation of SharePoint Server 2007 per a previous posting.
8. Install WSS SP1 and Office Server 2007 SP1; to version 12.0.0.6219.
9. Reboot (optional).
10. Install WSS SP2 and Office Server 2007 SP2; to version 12.0.0.6421.
11. Reboot (optional).
12. Install WSS SP3 and Office Server 2007 SP3.

References

• AlsTechTips: Build a Windows Server 2003 R2 (32) Clone Template
• AlsTechTips: Installing SharePoint 2007 on Windows Server 2003 Step-by-Step
• Microsoft Support: How To Create an Active Directory Server in Windows Server 2003
• Computer Networking Notes: How to configure ADS Active Directory Service Step by Step Guide
• Novell Knowledgebase: Installing IIS and ASP.NET v2.0
• Microsoft Download Center: Microsoft .NET Framework 2.0 Service Pack 2
• Microsoft Download Center: Microsoft SQL Server 2005 Express Edition Service Pack 4
• Microsoft Download Center: Microsoft SQL Server 2005 Service Pack 4 RTM
• MSDN Archive: SharePoint on the Web
• How to troubleshoot common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard on a computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007
• MSSQLServer Event ID: -1 - Cannot connect to [SQL Server Express instance]
• Matthew McDermott's Blog: Adventure Works Travel Site and Hands-on-Labs
• MSDN Archive: SharePoint on the Web (AdventureWorks site and labs)
• Microsoft office Updates: Office 2007 and SharePoint 2007 Service Pack 3 Availability
• Updates for SharePoint Products and Technologies
• Deploy software updates for Office SharePoint Server 2007
• Description of Windows SharePoint Services 3.0 SP3 and of Windows SharePoint Services 3.0 Language Pack SP3
• Description of the 2007 Office Servers SP3 and of the 2007 Office Servers Language Pack SP3
• Windows Installer 3.1 Redistributable (v2)
• Microsoft Office Updates: Announcing Service Pack 3 for Office 2007 and SharePoint 2007
• Microsoft Download Center: Microsoft .NET Framework 3.5
• Microsoft Download Center: Microsoft .NET Framework 3.5 Service Pack 1
• Microsoft Download Center: Microsoft® Silverlight™ 2 Software Development Kit
• SharePoint Server 2007 Sample: Creating a Custom User Site Provisioning Solution with Office SharePoint Server 2007

Notes

• Step 2: no roles were added to the clone template, during the clone template build process for Windows Server 2003 R2 Enterprise.  When adding a role to the machine for the first time, the Configure Your Server wizard will conveniently launch into adding the DC, DNS and DHCP roles.  It will also check the network adaptor settings and conveniently configure DNS forwarding automatically, based upon the settings it detects.
• Step 4: Windows Server 2003 R2 Enterprise has .NET Framework 2.0 already installed.  Verify this by downloading and running dotNETInspector.
• Step 5: I'm not sure why yet, but formally installing .NET 2.0 framework adds features and capabilities not originally there, even though Windows Server 2003 R2 is supposed to have .NET 2.0 already installed and this is verified by running .NET Inspector.
• Step 5: installing a more recent copy of the SharePoint Server 2007 requires not only .NET Framework version 2.0 but also .NET framework version 3.0.
• Step 5: installation of SP1 isn't necessary as it's rolled up into SP2. However, still good as an exercise.

Error: Failed to connect to the database server or the database name does not exist

Problem

You are attempting to run the SharePoint Products and Technologies Configuration Wizard after a fresh installation of the SharePoint Server 2007 binaries.  After entering initial configuration information,

and then clicking Next, you then see the following error:

Troubleshooting

1. Check logs:
• Reviewing the PSCDiagnostics log, at, C:\program files\common files\Microsoft shared\web server extensions\12\logs you find the following entry:

  System.Data.SqlClient.SqlException was thrown. Additional exception information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

2. Check data entry:
• You check the SQL Server instance name that you entered and verify that it is correctly entered.
• You check the account that you used, and verify that it has dbcreator and securityadmin roles configured.
3. Check remote connectivity:
1. You ping the SQL Server host from the SharePoint host and verify network access.
2. On the SQL Server host, you check the SQL Server surface area and find that both TCP and named pipes have been enabled:
   
3. On the SharePoint Server host, you test connectivity by installing SQL Server Management Studio and attempting to connect to the SQL Server host, but this fails, with the following message:

   Cannot connect to [your SQL Server instance]. ------------------------------ ADDITIONAL INFORMATION: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

4. On the SQL Server host, you check services and find that the SQL Server Browser service is disabled:
   

Resolution

• Start the SQL Server Browser service and set startup to automatic.

References

• MSSQLServer Event ID -1: Cannot connect to [your instance] 

Build a Windows Server 2003 R2 (32) Clone Template

Introduction

This posting compiles notes on building a Windows Server 2003 R2 SP2 32-bit server clone template for development and training purposes, for use with VMware Workstation 7.X. This procedure is based upon an evaluation copy of Windows Server 2003 R2.  Settings that are not specifically indicated below are default.  Creating the clone involves five discrete steps:

1. Preparing the VM
2. Installing Windows Server 2003
3. Configure Windows
4. Install VMware Tools
5. Sysprep

Other optional steps also covered here include: building a new VM from the clone and setting up Active Directory and DNS services.

Step 1: Prepare VM

 

Build a new VM using the following parameters:

1. Have both installation disks ready.
2. Start the procedure for building new VM using the following parameters.  Use the following configuration settings as you work through the New Virtual Machine Wizard:
   
1. Type of configuration: Custom (advanced)
2. Choose virtual machine hardware compatibility: Workstation 6.5-7.X.
3. Guest operating system installation: I will install the operating system later.
4. Select a Guest Operating system: Windows Server 2003 Enterprise Edition (not x64).
   
5. Name the Virtual Machine: Template2k3R2Sp2.
6. Processor Configuration:
1. Processors: 1
2. Cores: 1
7. Memory for the Virtual Machine: 1536
8. Network Type: Bridged
9. Select I/O Controller Types: SCSI Controller: LSI Logic
10. Select Disk: Create a new virtual disk
11. Select a Disk Type: SCSI
12. Maximum disk size: 25GB
• Allocate all disk space now: enabled
• Store virtual disk as a single file: selected
  

Step 2: Install Windows Server

1. Insert Windows Server 2003 R2 Enterprise SP2 disk 1 of 2
2. Power on VM.
1. Computer name: Template2k3R2Sp2.
2. Administrators password: [blank].
3. Network settings: Typical settings.

Step 3: Configuration

1. Install VMware Tools - typical installation
2. Disable Internet Explorer Enhanced Security.
   

Step 4: Install VMware Tools

1. On VMware Workstation, from the VM menu, select Install VMware Tools.
   
2. Reboot.

Step 5: sysprep

1. Insert the Windows Server 2003 R2 installation disk 1.
2. Create new folder at: root:\sysprep.
3. Navigate to: CDDrive:\Support\Tools\Deploy.CAB.
   
4. Copy contents of CAB file to new folder.
5. Double-click setupmgr.exe.
1. New or Existing Answer File: Create new.
2. Type of Setup: Sysprep setup.
   
3. Product: Windows Server 2003 Enterprise Edition.
4. License Agreement: No, do not fully automate the installation.
5. Wait for message stating "You have successfully completed...", then click Cancel button.
   
6. Verify File and Printer Sharing is installed.
7. Verify Server Service is running.  If not, start it.  Use Services.msc.
   
8. Double-click sysprep.exe.
1. Prompt: OK.
2. Dialog: keep all defaults, then click Reseal button.
• NOTE: if this prompt appears, leave it be (don't click OK), then verify that the Server service is started.  If not, start it and then return to the prompt, click OK, and then click Reseal again.
  
3. Prompt: OK.
   
9. Shutdown (automatic).

Optional: Build new machine from clone

1. Right-click on the template, and then select Clone.
2. Select the following settings at each window of the Clone Virtual Machine Wizard:
1. Clone from: The current state in the virtual machine.
2. Clone method: Create a full clone.
3. Click Close.  Clone operation will take approximately five minutes.
4. Power on new machine.  Windows Setup Wizard starts.
5. Configure new settings as needed.

Optional: Configure Domain Controller

1. From the Start menu, select Manage Your Server.
2. On the Manage Your Server page, click Add roles.  The Configure Your Server Wizard appears.
   
3. Click Next.
4. On the Configure Options page, select Typical configuration for a first server, and then click Next.
5. On the Active Directory Domain Name page, enter a domain name, and then click Next.
6. On the NetBIOS page, click Next.
7. On the Summary of Selections page, click Next.  At the prompt, click OK.
8. On the Server Configuration Progress page, click Next.
9. On the This Server is Now Configured page, click Finish.
   
10. View the Configure Your Server log: C:\Windows\Debug\Configure Your Server.log.
11. On the Manage Your Server page, click Add or remove role.
12. Click Next.
13. Select DHCP, and then click Next.
    
14. Enable the checkbox, and then click Next.  This removes DHCP.

Summary

This posting collates and archives notes on creating a template for Windows Server 2003 R2 Enterprise.

References

• Microsoft TechNet: Windows Server 2003
• Microsoft TechNet: Installing Windows Server 2003 R2
• Microsoft TechNet: Modifying Enhanced Security Configuration Settings
• Microsoft TechNet: Windows Server 2003 Service Packs
• James Kovacs' Weblog: How to Sysprep Windows
• Velocity Reviews: sysprep incompatibility
• Rony's Blog: SYSPrep windows 2003 R2
• Microsoft TechNet: How to Install Active Directory on Windows Server 2003
• Microsoft TechNet: Start or stop a DHCP server
• Microsoft TechNet: Remove or uninstall DHCP
• Download Center:
• Microsoft Windows Server 2003 R2 Enterprise Edition VHD

Notes

• There is an incompatibility between this tool and the current operating system.  Unable to continue: verify that the Server service is running.