Following are the procedures to setup Server redundancy and starting/stopping of remote projects on Vista and Windows Server 2008:

Important: You must be a user in the administrators group to set up server redundancy on a remote machine that is part of a Workgroup.

	Server Redundancy Setup
		On the primary and secondary servers
		On the secondary server
		On the primary server
	Remote project start from the Workbench

Server Redundancy Setup

On the Primary and Secondary Servers

Do the following on both the Primary and Secondary servers

1. Follow the CIMPLICITY documentation requirements for Server Redundancy to set up the hardware and network, including

Hardware.

Computer.

Network.

2. Create the same user on both servers.

The user must:

Be in the Administrator group

Have the same user name on both servers.

Have the same password on both servers.

3. Configure the machines to be in the same workgroup.

4. Do the following in the Windows Firewall.

1. Select Start>Control Panel>Windows Firewall.

2. Select the Exceptions tab.

3. Check the following.

File and Printer Sharing

Netlogon Service

4. Click OK.

5. Configure the network(s) between the computers as Private.

On the Secondary Server

Note: If you want to start the project on the primary server from the secondary server, you also have to do these procedures on the primary server,

1. Open the Control Panel>Network and Sharing Center.

2. Make sure the following are enabled.

File sharing

Password protected sharing

3. Edit the Registry to access a remote WinRM service in a workgroup, as follows.

Note: If the account is a local computer member of the Administrators group, the User Account Control  (UAC) does not allow access to the WinRM service.

Warning: Making changes to the registry is very dangerous and should be done with care.

1. Run regedit.exe or regedt32.exe.

2. Expand the following folders in the Registry Editor left-pane.

1. HKEY_LOCAL_MACHINE

2. SOFTWARE

3. Microsoft

4. Windows

5. CurrentVersion

6. Policies

7. System

3. Right-click System in the left pane; select New DWORD (32-bit) Value on the Popup menu.

4. Enter LocalAccountTokenFilterPolicy in the new field that displays in the Registry Editor right-pane.

5. Press Enter.

6. Double click LocalAccountTokenFilterPolicy

7. Enter 1in the Value Data field.

8. Click OK.

9. Close the Registry Editor.

4. Set Remote Registry startup to Automatic, as follows.

1. Open the Control Panel>Administrative Tools>Services.

2. Right-click Remote Registry; select Properties.

3. Select Automatic in the Startup type list field.

On the Primary Server

Configure project with server redundancy and use a UNC path name for the Project path under the Redundancy tab on the Project Properties.

Remote Project Start from the Workbench

The following procedure enables selected users to start a remote project from the Workbench.

On the Computer that will start a project on a remote computer.

1. Map a drive from remote computer to the local computer to access the project.

2. Grant full access for each administrative user who will perform administrative tasks, including configuration update, dynamic configuration, as follows.

1. Open a command window.

2. Enter the following.

net share  /grant:Username1,FULL [/Grant:Username2>,FULL] [/Grant:UsernameN>,FULL]

Where

Sharename=drive:path	Drive and path of the share
Username	You can enter as few as one name to as many names as should have this privilege. Username1 is the first name entered for selected users. Username2 is the second user name for selected users. UsernameN is the user name with N corresponding to the sequence number for selected users.
FULL	Grants full access.

3. Continue setup using the same procedures that you use to set up server redundancy.

More information

Server redundancy configuration procedures.

---