Database Availability Group (DAG)

Database Availability Group (DAG)

Now that Exchange 2010 has been officially released and I am allowed to blog on the topic I wanted to start with what I believe is one of the best features added to Exchange 2010. There may be some heart break of the removal of a few features from Exchange 2007 however Database Availability Groups (DAG) is a feature that has been ask for over years. To better under what a DAG is let’s recap through Exchange.

Exchange 2007 introduced LCR, CCR, SCC and SCR
LCR (local continuous replication) this was mainly used for small business who wanted to replicate a copy of their Exchange database to another disk on the same server.

SCC (Single copy cluster) was what I would call a traditional Exchange cluster which used shared storage to host the Exchange database.

Basic architecture of an SCC

CCR (cluster continuous replication) was used to replicate Exchange database information between 2 Exchange server allowing for hardware and storage redundancy but was limited to 1 Active node and 1 Passive node.

Basic deployment of CCR

SCR (standby continuous replication) was introduced in Exchange 2007 SP1 to provide the ability to replicate Exchange databases to an disaster recovery location.




How did it use to work?

The concept of a DAG and how it functions I believe is easier learned by someone who hasn’t worked with Exchange clusters previously.

In Ex 200X an Exchange server was installed as either an Active or Passive cluster node at the time setup.exe was run.

Depending on which version of Exchange you installed you had to create an Exchange virtual server (EVS) which was changed to cluster mailbox server (CMS) in Exchange 2007.

When a user connected Outlook the mailbox server name was a clustered resource which moved between any number of nodes on the Exchange cluster. This allowed for no end user configuration changes all the resource moved between physical servers
An Exchange database was associated with the clustered resource and when you open EMC/ESM the only Exchange server name that was shown was the clustered node, let’s call is CMS1. That means database one would always belong to CMS1 even when this moved between physical machines.

Here comes the DAG

So now it’s time to forget everything that I just mentioned previously in this article about Exchange clustering.

What has been removed?

1. No more EVS/CMS
   
2. Database is no longer associated to a Server but is an Org Level resource
   
3. There is no longer a requirement to choose Cluster or Non Cluster at installation, an Exchange 2010 server can move in and out of a DAG as needed
   
4. The limitation of only hosting the mailbox role on a clustered Exchange server
   
5. Storage Groups have been removed from Exchange
   

Is anything the same?
1. Window Enterprise Edition is still required since a DAG still uses pieces of Windows Failover Clustering
What’s New?

 1. Other roles can be install on the mailbox server when it is a member of a DAG
2. A database name must be unique in the Exchange Org

 Let’s walk through the installation of  Exchange 2010 and then setup our DAG

I am going to pickup where I left off in the following post http://www.exchange-genie.com/2009/04/exchange-2010-installing-the-mailbox-role/ where we walked through the exchange installation.
1. Open EMC -> Expand Orgnaization componets and select the database availability group tab

2. Right click and select New Database Availablity Group

3.  We are now ask to fill in 3 pieces of information for our DAG
a.  DAG name
b.  FileShare witness (fsw)  UNC path (can be any machine)
c.  phycial location on the server that will host the fsw

You can see I am using my DC in the lab for the fsw machine, note that whatever machine you are using as the fsw needs to have the Exchange Trusted Subsystem group in the local Admins group

4.  Click Finish on the completion page

We have now created our first DAG, if we open active directory users and computers we will see a computer objects gets created with the DAG name we supplied

This object is used by Windows clustering
After the wizard completes we can verify in EMC that our DAG was created as well

by itself the DAG does not do anything for us and there are no properties to manage in EMC, however if we use the shell we can see a few additional properties like:
NetworkCompression                 : InterSubnetOnly
NetworkEncryption                  : InterSubnetOnly

[PS] C:\>Get-DatabaseAvailabilityGroup | fl

Name                               : GenieDAG
Servers                            : {E14-EX1}
FileShareWitnessShare              : \\E14-DC1\GENIEFSW
FileShareWitnessDirectory          : C:\GENIEFSW
AlternateFileShareWitnessShare     :
AlternateFileShareWitnessDirectory :
NetworkCompression                 : InterSubnetOnly
NetworkEncryption                  : InterSubnetOnly
DatacenterActivationMode           : Off
StoppedMailboxServers              : {}
StartedMailboxServers              : {}
OperationalServers                 :
ControllingActiveManager           :
ReplicationPort                    : 0
NetworkNames                       : {}
AdminDisplayName                   :
ExchangeVersion                    : 0.10 (14.0.100.0)
Identity                           : GenieDAG
WhenChanged                        : 4/17/2009 7:22:42 PM
WhenCreated                        : 4/17/2009 7:22:42 PM
OrganizationId                     :
OriginatingServer                  : E14-DC1.ExchangeGenie.Local
IsValid                            : True
Lets add our first node to the DAG
1. in EMC right click our DAG and select manage database availability group

2.  On the manage database availability group page click the Add button

3. In  the select mailbox server window select the appropriate mailbox server in my case its e14-ex1

4.  click Manage

after selecting manage Windows clustering is installed at this time

5. Click finish on the completion page

6. We can now see that E14-ex1 was added to the DAG


If we open our Admin tools we will see the Windows clustering is installed and that E14-ex1 is a member of the cluster

note: by default the DAG is set to use DHCP to assign and address to it, in the current build there is no way to assign an IP to the DAG in gui. This can be done when adding a node to the DAG from EMS.
Let see what it looks like to add the server from EMS
1. Open EMS (use the local shell currently) add-databaseavailabilitygroupserver GenieDag -mailboxserver E14-ex1 -databaseavailabilitygroupIpAddress 192.168.1.60

Let open Windows Failover Clustering and see that the IP is assigned to the cluster.
 
Another item you will notice that is different from previous versions of Exchange is there are not clustered resources, no disks, not CMS/EVS.
The DAG only users Windows Clustering for hear beat and quorum the new Active Manager is used to manage the DAG failvoer.
We have currently created a DAG with only 1 Exchange server which does not do us any good as DAG nodes can only replicate to another server, so we will need to add another node.

Backup Exec service is not runing in symantec backup server

Check for a process called "LUGetUpdatesExe.exe" and kill it - afterwards services should start up again. To avoid this happening again disable Live Update then

How to use BEMIG to manually upgrade the Backup Exec database from a previous version

Product(s)

• Backup Exec

Subject

• Troubleshooting
• Installing

• Italiano
• 한국어 (Korean)
• 中文 (简体) (Simp. Chinese)
• 中文 (繁體) (Trad. Chinese)
• Show less

Problem

Need to manually upgrade Backup Exec from a previous version.

Solution

The recommended upgrade method is to allow the Backup Exec (BE) installer upgrade BE and its database during the installation. If that fails to occur or a saved database from a previous BE version needs to be added to a newer BE version, the BEMIG tool can be used. This tool follows the same upgrade version rules that the BE installer has. This is noted in the chart below.
Note: If the .mdf and .ldf files are from an older version of Backup Exec installed on a different server then please do not follow the procedure below if any of the following are true:

• Backup Exec is clustered.
• The Backup Exec Shared Storage Option (SSO) is installed.
• The Backup Exec Server Free Option is installed.
• The computer where Backup Exec is installed and the computer where it will be installed are running two different versions of the Windows Operating System.
• If planning to move Backup Exec to a different drive/directory on the server.
• If upgrading from one version/revision (build) of Backup Exec to another

Steps:

1. Confirm BE is working in its current database first.

2. Stop the all Backup Exec services (including the  SQL(BKUPEXEC) service)
3. Open the \Program Files\Symantec\Backup Exec Directory.  Copy the Data folder and paste it in the same location. Rename the "Copy of Data" to "Data-'TodaysDate' or "Data-Version#-New"

4. Copy the saved Database from the previous BE version into the Backup Exec\Data folder.
   This will be bedb_dat.mdf and bedb_log.ldf files.

5. If the Catalogs have been saved also, rename the Catalogs to Catalogs.old, then copy/move the saved catalogs under Backup Exec.

6. Start the SQL service.

7. Set the registry keys for BEMIG.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

7a. Launch the Registry Editor (Start, Run, Regedt32).
     Navigate to HKLM | Software | Symantec | Backup Exec for Windows | Backup Exec | "VersionNumber" | Install             
   


7b. Modify the value of "Upgrade" to 1.
      (Create as a Dword if it is not present)

7c. Modify the value of  "Upgrade Version" to the version of the DB being imported. See chart.
      (Create as a String value if not present)
Please refer the following Table while setting the value for Upgrade version Key.

PRODUCT VERSION	UPGRADE VERSION	10	10D	11	11D	12.0	12.5	2010	2010 R2
9.1 revison 4691	9.1.4691.0	X	X	X
10.0 revison 5484	10.0.5484.0	X	X	X
10.0 revison 5520	10.0.5520.0		X	X
10.1 (10d) revison 5629	10.1.5629.0			X	X	X
11 revison 6235	11.0.6235.0				X	X
11 (11d) revison 7170	11.0.7170.0					X	X	X	X
12.0 revison 1364	12.0.1364.0						X	X	X
12.5 revison 2213	12.5.2213.0							X	X
2010 revison 2896	13.0.2896.0								X
2010 R2 revison 4164	13.0.4164.0

  8.Open a CMD command prompt to \Program Files\Symantec\Backup Exec
  Run BEMIG
  Wait for it to fully complete and return to a new prompt.

9. Start BE services and open the BE console.

Note, if the services fail to start, you may need to do additional steps of:

1. Stop the SQL(BKUPEXEC) service
2. Copy the BEDB database files from the Data folder to the desktop
3. Start the SQL(BKUPEXEC) service
4. Run BEutility Copy Database to import the desktop BEDB files. This will correct any Environmental changes effecting the database.
              Copy Database Document -  http://support.veritas.com/docs/286093

How to migrate (move) Backup Exec from one system to another with the same version of BE, Windows and same or different computer names.

Product(s)

• Backup Exec -> 12.0 -> 12.5
• Backup Exec -> 12.0
• Backup Exec -> 11d (11.0)
• Show all
• Backup Exec -> 10.0 -> 10d (10.1)
• Backup Exec -> 2010 -> 2010 .R2
• Backup Exec -> 2010
• Show less

Problem

How to migrate (move) Backup Exec from one system to another with the same version of BE, Windows and same or different computer names.

Environment

Instructions for moving Backup Exec (tm) 10d or above to another computer system which has the same version installed. The target systems can have the same computer name or a different computer name.

 

 

The information in this TechNote applies to the following scenarios: 
 

• Moving an installation of Backup Exec from one 32-bit system to another 32-bit system.
• Moving an installation of Backup Exec from one 64-bit system to another 64-bit system.
• Moving an installation of Backup Exec from a 32-bit system to a 64-bit system.
• Moving Backup Exec to another system where the Backup Exec Database (BEDB) is installed on a SQL 2000, 2005, or 2008 instance.
• Moving Backup Exec to another system where the system being moved is a Central Administration Server (CAS).
• Moving DLO from one Backup Exec system to another Backup Exec system. 

Do not follow this procedure if any of the following are true: 
 

• Backup Exec is clustered.
• The Backup Exec Shared Storage Option (SSO) is installed.
• The Backup Exec Server Free Option is installed.
• The computer where Backup Exec is installed and the computer where it will be installed are running two different versions of the Windows Operating System.
• If planning to move Backup Exec to a different drive/directory on the server.
• If upgrading from one version/revision (build) of Backup Exec to another.

NOTE:  If any of the above mentioned conditions are true, this procedure cannot be performed and Backup Exec will need to be re-installed and re-configured.

NOTE: Prior to moving Backup Exec versions from one system to another the following upgrade paths need to be followed:
 

• When moving from a 32-bit system to a 64-bit system it is recommended that any Backup Exec version upgrades should be performed on the 32-bit system first prior to following the instructions contained in this TechNote.

Solution

Instructions for moving an installation of Backup Exec

The Backup Exec move process consists of five sections:

I.  Prepare the current Backup Exec installation on the source computer system.

II.  Move Backup Exec data to a temporary storage location.

III. Install Backup Exec on the new Backup Exec target media server.

IV. Move the Backup Exec data from the temporary storage location to the new target Backup Exec media server.

V.  Verify that the new Backup Exec installation matches the original Backup Exec installation.

Important Note: Do not remove Backup Exec from the original computer until the migration of data and media to the new Backup Exec media server is complete. It must be verified that the new Backup Exec installation matches the original installation.

I.   Prepare the current Backup Exec installation:

In order to move Backup Exec from one computer to another, the following preparation must be performed on the original Backup Exec media server:

1.  Backup Exec Version and Revision Number - Write down the Backup Exec version and revision number listed on the Backup Exec Help | About Symantec Backup Exec for Windows Servers menu.
 

2.  Update Backup Exec Software - Install all the Backup Exec software updates (hotfixes and service packs) available for the Backup Exec version and revision currently installed. Software updates can be obtained from either the Backup Exec Technical Support site ( http://www.symantec.com/enterprise/support/downloads.jsp?pid=15047) or Symantec LiveUpdate.

3.  Installed Backup Exec Options, License Keys, and Installation Path - Write down a list of the installed Backup Exec options, license keys and the installation path from the existing Backup Exec installation.

To obtain this information, follow these steps:

Open Backup Exec. Select Tools | Install Options and License Keys on this Media Server from the Backup Exec menu. After the license keys are obtained, precede through the install screens to obtain the install path. Once this information is obtained, the install can be canceled.
 

 

Figure 1 - Record Backup Exec License Keys
 
 

Note:  Backup Exec keeps a record of the Backup Exec license keys currently installed in a file named BESERNUM.XML. This file is located under Documents and Settings\All Users\Application Data\Symantec\Backup Exec. The license keys listed in this file can be imported (see Figure 1) during the installation on the new Backup Exec media server instead of manually entering the license keys. To use this file during the installation of the new Backup Exec media server, save the file to location on the new Backup Exec media server so it can be retrieved when needed.

4.  Identify backup-to-disk folder locations - Write down the path of all backup-to-disk folders. To obtain this information, follow these steps:

a. Open Backup Exec.
b. Select the Devices view.
c. Highlight Backup-to-Disk Folders, right click and select properties. 

Note location of B2D folder (see figure 2)
Figure 2 - Backup to Disk folder location

II. Move Backup Exec data to a temporary location

Perform the following steps on the original Backup Exec media server:

Note: If the server in question that is being moved is a CAS server, then prior to shutting down the services ensure that all of the Backup Exec services for each Managed Media Server that communicates with the CAS are shut down as well.

1.  Stop all Backup Exec and DLO (if installed) services - Using the Windows Services applet; stop the following Backup Exec services: (Figure 3 and Figure 4)
 

• Backup Exec Agent Browser
• Backup Exec Device and Media Service
• Backup Exec DLO Administration Service (only if DLO is installed)
• Backup Exec DLO Maintenance Service (only if DLO is installed)
• Backup Exec Job Engine
• Backup Exec Remote Agent for Windows Servers
• Backup Exec Server

2. Stop the Backup Exec SQL Server service (a separate DLO Instance will also exist with 10d)
 

• SQL Server (BKUPEXEC) - This is a SQL Express instance. Stop this instance if it is the instance that the Backup Exec (BEDB) and DLO (BE_DLO) databases are using.
• SQL Server (MSSQLSERVER) - This is SQL Server instance (local or remote). This is a default SQL instance. This can be a SQL 2000, SQL 2005, or SQL 2008 instance.  Stop this instance if it is the instance that the Backup Exec (BEDB) and DLO (BE_DLO) databases are using.
• SQL Server (SQL2005ONE) - This is a SQL Server named instance (local or remote). This can be a SQL 2000, SQL 2005, or SQL 2008 instance.  Stop this instance if it is the instance that the Backup Exec (BEDB) and DLO (BE_DLO) databases are using.

 Figure 3 - Backup Exec and DLO Services

 

Figure 4 - SQL Service where Backup Exec and DLO databases are installed

 

 

6.  Copy Files - Using Windows Explorer, copy the following Backup Exec directories (files) to a temporary location keeping the directories separate:
 

• C:\Program Files\Symantec\Backup Exec\Data

 IMPORTANT NOTE - Do NOT copy the msgq*.*.dat files over to the temporary location (see Figure 5)

 

Figure 5 - BE\CASO message queue files

 

• C:\Program Files\Symantec\Backup Exec\Catalogs

NOTE: If this is a CAS server, make sure to copy over the Catalog folders for the Managed Media Servers as well. These should all be listed under the Catalogs folder.

• C:\Program Files\Symantec\Backup Exec\IDR (if present)
• C:\Program Files\Symantec\Backup Exec\Reports\Saved
• Backup-to-Disk folders as mentioned in section I - step #4 above (if created)

Note: The only files that must be copied over are the B2D*.*.bak files. These are the actual media (see Figure 6)

 

Figure 6 - Backup to Disk Media

 

Important Note:  At this point, if the source computer name is the same as the target computer name then turn off the source (32bit computer) and turn on the target (64bit computer). The domain/workgroup information should also match.

 

III. Installing Backup Exec on the new Backup Exec media server

Perform the following steps on the new Backup Exec media server:

1.  Install Backup Exec - Install the same version and revision of Backup Exec that is installed on the original Backup Exec media server. If moving to a 64-bit system, use the 64bit Backup Exec installation CD instead of the 32bit installation CD.

NOTE:  When prompted for Backup Exec license keys, enter the Backup Exec license keys from the original Backup Exec media server. If using the Backup Exec license keys file BESERNUM.XML to enter the license keys, select the Import button (see Figure 7) and point to the location of the saved license key file.
 

 

Figure 7 - Import License Keys from Source System
 

NOTE:  When prompted for the installation path, use the same path as the original Backup Exec media server. For example, if the path C:\Program Files\Symantec\Backup Exec\ was used in previous installation, then use the same path.

NOTE: The SQL install path can be changed. If the Backup Exec (BEDB) and DLO (BE_DLO) databases were installed to a SQL Express instance, the databases can be moved to another non SQL Express instance. The database files can be moved to any SQL 2000, 2005 or 2008 instance as long as the database files are being moved to the same or newer version of SQL (i.e. SQL 2008 files cannot be moved to a SQL 2005 instance and SQL Server files cannot be moved to a SQL Express instance).

2.  Reboot - Restart the computer (do not open Backup Exec after rebooting).
 

3.  Install Updates - Install all the Backup Exec software updates (hotfixes and service packs) available for the Backup Exec version and revision currently installed.  Software updates can be obtained from either the Backup Exec Technical Support site (http://www.symantec.com/enterprise/support/downloads.jsp?pid=15047) or Symantec LiveUpdate.

4. Reboot - Restart the computer (do not open Backup Exec after rebooting).

 

IV. Move Backup Exec data from the temporary location to the new Backup Exec media server

Perform the following steps on the new Backup Exec media server:

1. Stop all Backup Exec services - Stop all Backup Exec services (a list of Backup Exec services can be found earlier in this TechNote Section II - Step #1).

2. Stop the SQL Service (a list of Backup Exec services can be found earlier in this TechNote, Section II - Step #2).

3. Copy Files - Copy the Backup Exec files from the temporary directories, overwriting the data, catalogs, and Intelligent Disaster Recovery (IDR) folders on the new system.

4. On the new or target system, create a folder where the new Backup to Disk folders will reside.  Copy the saved off .bkf file(s) from the temporary location into this folder.

NOTE: Perform Step 5 only if you are moving the installation to a system with a DIFFERENT computer name. If the installation is being moved to a system with the SAME computer name, skip this step and go to the next step, step 6. Step 5 is required because the new database will have the name of the old database and will have to be changed before the Backup Exec services can start.

5. Rename the DataPartition name for the Backup Exec Database that was copied.

Refer to the steps mentioned below:

a. Start the SQL Server (BKUPEXEC) service or SQL Service where Backup Exec is installed.
b. Open a command prompt and type Sqlcmd -E -S servername\BKUPEXEC
c. If successfully connected to the server, the following prompt appears: 1>  This indicates a connection to the Backup Exec instance using Sqlcmd (see Figure 8).
 

 

Figure 8 - Make a Connection to the SQL Instance
 
 

·Run the following query from either Sqlcmd or from the SQL Management tools:

 

Use bedb

<Press enter>

Type go

<Press enter>

SELECT partitionname FROM datapartition

<Press enter>

Type go

<Press enter>
 

 

After pressing ENTER the original server name is listed.  Running this query will yield the current database partition name that the database has (which is the old one)

Change this name from the original server name to the new Backup Exec  server name by typing the command below. This will update the database with the partition name of the new server.

 

UPDATE DataPartition SET PartitionName='<this server name>' WHERE PartitionID =0

<Press enter>

Type go

<Press enter>

 

· Run the select statement again and verify that the name was changed to the new server name:

 

SELECT PartitionName FROM DataPartition

<Press enter>

Type go

<Press enter>

 

Figure 9 shows what the process looks like...

 

Figure 9 - Query Display for Changing Computer Name in the Database

 

 

· Type quit to exit Sqlcmd

6. Start all Backup Exec services - Start all the Backup Exec services which were stopped in Step 1.

 

V.  Verify that the new Backup Exec installation matches the original Backup Exec installation

Perform the following steps on the new Backup Exec media server:

 

1. Start Backup Exec - Start the Backup Exec application and verify that the Backup Exec data was correctly moved.

· Verify that the Jobs, Selection Lists, Policies, Alerts, and Job History are correct

2. In Backup Exec go to Devices Tab; the old server name with off-line devices should be listed under the source server name (see Figure 10).
 

 

Figure 10 - Off line devices from the Old System
 

Delete the old server (source) entry and its devices by right clicking on the device and selecting Delete.

3. Clean out media not being used - If there is media from devices that are no longer in use, clean this up from the new Backup Media Server as well (see Figure 11). From the Media Tab, move all of the offline media that will no longer be used over to the retired media set and delete it.
 

 

Figure 11 - Media from Source that is no Longer being used
 
 

 

4. Create a new Backup to Disk folder under the current (target) server's Backup to Disk devices and recreate catalogs.

a. Create a new folder for the B2D media and configuration files.
b. Copy the B2D media from the temporary location into the folder just created
c. Create the B2D folder and point to the path of the new folder (see Figure 12)
d. Run an inventory job on the B2D media
e. Run a Catalog job on the B2D media

NOTE: If the Target server is a CAS, run the inventory and Catalog job on the Media after the CASO Configuration changes (listed in the CASO Configuration section below) have been performed.
 

NOTE: If a catalog job is run on Media on the CAS or MMS(s) the media is now considered imported and may be subject to be overwritten. Check the media overwrite protection that is currently configured to ensure that media that is needed will not be overwritten.
 

Figure 12 - Backup to Disk create on Target System

 
 

 

5. Review the Backup Selections Lists. If the old server was being backed up locally, it will need to be changed to backup remotely under remote selections. Viewing the selections in text mode may be necessary to remove the old server local selection. Additionally, the new server will need to be added to the selection list if it needs to be backed up (see figure 13).

 

Figure 13 - Update Source System Local Selections on Target System
 
 

 

6.  On each of the remote machines that are backed up (if any), vxmon.exe needs to be run to point publishing to the new box. Open "C:\Program files\Symantec\Backup exec for windows\RAWS\Vxmon.exe", click on the Publishing tab, add the new server.  If the old server is listed, remove it.  

Configuration Steps for Target Server if it is a Central Administration Server (CAS)...

If the new Media server is a Central Administration Server (CAS) and it has attached Managed Media Servers than the following additional steps should be performed...

The MMS(s) should be in a no-communication state since its services were shut down earlier (see Figure 14)
 

Figure 14 - CASO Managed Media Server in Unavailable State
 
 

1. Delete the current msgq files on the Managed Media Server (see Figure 15). These message queue files are associated with the old CAS and will get regenerated on the Managed Media Server during service startup. Navigate to the data folder where these files are stored. The default location is C:\Program Files\Symantec\Backup Exec\Data
 

Figure 15 - CASO Managed Media Server files
 
 

2. Change the Managed Media Setting to communicate with the new CAS

If the new Central Administration Server (CAS) was just moved from one computer system to another but the name has remained the same, then just start up the services on the Managed Media Server and it should show as On-Line and Manageable from the Central Administration Server.

However, if the new Central Administration Server was moved from a system that has a different name, then some registry keys on the Managed Media Server will have to be changed in order for the Managed Media Server to communicate with the new Central Administration Server.

The keys that need to be changed are as follows...
 

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

 

HKLM\Software\Symantec\Backup Exec for Windows\ADAMM\

 

Change the Database Server Name key to the new server name

 

If the instance name has changed as well, then the Database Instance Name key will also have to be changed to the new instance name. If the source system used a named SQL instance but the target now uses a default instance, then the instance name should be removed from the instance name key.

 

Note: If the Managed Media Server is not sharing the database on the Central Administration Server than changing this ADAMM key should not be necessary. It should point to the local server, which is the Managed Media Server.

 

HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Server\

 

Change the DjmPrimaryServer key to reflect the name of the new Central Administration Server. Changing this key ensures that communication through the Message Queue can now take place between the new CAS and the MMS.

3. Start up all of the Backup Services on the Managed Media Server(s). Once these services are started the MMS(s) should now display as available from the CAS.

4. Catalogs for the CASO environment:

• For the Central Administration Server and for the B2D folder and media that is on the CAS, run an Inventory and Catalog job to retain the catalogs for the CAS media.
• If there are MMS(s) that have their catalogs Centralized and the catalogs were copied, as noted in Step #6 of Section II above, then they should show up under Restore selections on the CAS. If the catalogs do not show up, then, from the CAS, run an Inventory Job and Catalog job on the device\media for that particular MMS.
• If there are MMS(s) that have their catalogs Distributed and the catalogs were copied, as noted in Step #6 of Section II above, then they should show up under Restore selections on the CAS. If the catalogs do not show up, then, from the MMS, run an Inventory Job and Catalog job on the device\media for that particular MMS.

NOTE: If a catalog job is run on Media on the CAS or MMS(s) the media is now considered imported and may be subject to be overwritten. Check the media overwrite protection that is currently configured to ensure that media that is needed will not be overwritten.

Configuration Steps for Target Server if it is a DLO (Desktop and Laptop Option) Server...

The DLO database has no configuration requirements on the database name so no changes will have to be made to the database in order to use DLO on the target server. However, there are some configuration changes that need to be made to the DLO Server and Desk Top agent in order to use DLO with the new target server.
 

Figure 16 - Create new DLO Storage Location
 

1. If the old Storage Location was on the source server and the source server will be put of commission, it may be necessary to create a new storage location (see figure 16) on the target server or on another server that can hold the user DLO Data.

NOTE: If the source server is not being put out of commission, the old Storage location still can used if the user wishes to do so.
 

Figure 17 - Move user data from old Storage Location to new Storage Location
 

2. If it has been determined that the DLO user data needs to be transferred to a new Storage Location, then the user can transfer the data by opening the DLO Console, selecting the user, and then select to Move the Network User Data Folder (see Figure 17).
 

Figure 18 - Change Automated User Assignments to new Storage Location
 

3. If the Storage Location has been changed, it will be necessary to change the Automated User Assignments. Select the name from the Automated User Assignments (See Figure 18), and change the Storage Location to the new Storage Location.
 

Figure 19 - SQL Server Configuration for Named Pipes
 

4. Once the DLO database has been moved to another SQL instance it is necessary that you check the SQL Server protocol Named Pipes and ensure that this protocol is enabled (See Figure 19). DLO uses this protocol for its Desk Top Agent. If this protocol is not enabled, the Desk Top Agent will not be able to communicate to the DLO Server.

NOTE: Once the Named Pipes protocol is enabled, it will be necessary to restart the SQL Service for the change to take place.

5. Once the SQL Protocols are configured, the DLO agents on the Desk Tops and Laptops should find the new Server and connect to it. Check the options on the Agents to ensure that the Storage Locations (if moved) are correct (See Figure 20). If they are not correct, it may be necessary to uninstall and then reinstall the agent so that they properly pick up the correct configurations from the server.

NOTE: if the Agents are uninstalled, be sure to select NO to the option to uninstall the user data from the Desk Top\Laptop. If this is not done, the user will only be able to retrieve data from the server.
 

Figure 20 - DLO Desktop Agent Properly Communicating with DLO Server
 

/apps/media/inquira/resources /resources

Fix: Infinite “Configuring Updates 3 of 3. 0% complete.”

Posted in Fixes | Comments (20)

This one was apparently fixed by Microsoft a while ago but in case you run into something similar it’s helpful. It will work on any problem where an update has hijacked the screen with an “Update in progress” type of message and won’t let you finish booting windows. This fix will clear that bad update.

Problem: You run Windows Update and select your updates. Once they download everything they prompt you to restart your system. You do so, the computer turns off then on again and windows starts to boot until you see a screen saying: “Configuring updates 3 of 3. 0% complete.” No matter how long you wait and no matter how many times you restart the screen does not go away.

Fix: You need to delete the “pending.xml” file. The file has a list of updates and forces windows to install those updates at startup. By deleting the file you delete the list so Windows ignores the updates.

THE FIRST METHOD:

Microsoft has a fix for this problem up on their website (here) and we’ll take a look at that method first.

The Microsoft “fix” basically tells you to use restore points to send your computer back in time. How far back? Well just far enough so that your computer is in a state before the broken updates were downloaded. The closer this date is to the present the better. If you restore too far back you end up with programs that don’t work and have a confused computer.

So how do you restore without being able to boot into windows? Again, there are two methods:

1. Take your Vista disc and insert it into the computer. Ensure that your booting with the CD and when the disc loads press “R” as soon as you see the option. Invoking this command will launch the repair section of the Windows CD which contains a System Restore program. Just select the closest time to the present and restore to that.
2. Boot into safe mode.
3. Click Start, a menu will pop up.
4. Click Run from the menu. A window will pop up.
5. Type in: “rstrui.exe” This will launch the system restore utility.
6. Select the closest restore point to the present.

After the restore is done you will find that you can boot into windows once again! There is one more step that you need to do. Microsoft recommends installing an update to windows update, crazy eh? You can find that update here make sure that you download and install this right away.

THE SECOND METHOD:

Now in case for some reason the restore point solution doesn’t work for you there is a second method. I got this fix from a fellow tech and unlike the recovery points method this one just modifies the “pending.xml” file. What you basically need to do is delete “pending.xml”. It is not a file that can be deleted easily when you don’t have access to Windows. But of course our favorite tool comes in handy again-

Download and install a copy of The Ultimate Boot Disc for Windows it’s a useful tool to have for these and other kinds of windows problems. Boot from the disc and in the menu that pops up choose Ultimate Boot Disc for Windows (or something of the like.) The next step will take a few moments so get some coffee, or alcohol depending on your mood. There! You will see that we have loaded a modified version of Windows! One filled to the brim with cool tech tools!

Select the “Computer” or “My Computer” icon. This will launch a folder with a list of all of your drives. Select the drive that contains your windows installation.

1. Click on the Windows folder.
2. Click on the Winsxs folder.
3. Find the file pending.xml.
4. Right click>Properties.
5. Go to the Permissions tab and give yourself full control over the file.
6. Click Apply.
7. Delete pending.xml.

Once we delete the “pending.xml” file windows no longer looks to it for instructions to install updates and we are free to boot into windows normally.

The next time you download updates that need to be installed Windows will recreate the pending.xml file with new correct updates and you’ll be good to go. Once you get into Windows don’t forget to download and install the windows update fix, it can be found here.

How to explain this problem to the client:This is caused by a bad update Mr. Customer, you know how Microsoft is (insert bonding laugh here.) I’ve usually seen it affect HP/Compaq AMD based unit mostly and you will now be safe from this error in the future. Hooray!

Deploy Junk E-mail Lists Throughout Your Organization

As we know, we can set Outlook's "Safe Senders list", "Block Senders list" and "Safe Recipients list" to help people protect Spam. However, allowing all users to modify their lists is time-consuming and inconvenient. Now, we can use the following steps to deploy such lists throughout your organization (we will use "Safe Sender list" as example).
 
1. Create a share folder on server, say Junk E-mail, and give everyone read permission. Create a text file name SafeSender.txt. Input email addresses into file (one address one line).
2. Install "Microsoft Office 2003 Resource Kit" on the Domain Controller.
3. Start Active Directory Users and Computers (ADUC), Right Click on the OU in which users account is present, Go To "Properties", Click on "Group Policy" tab.
4. Select the Policy in effect, click on "Edit". It will open "Group Policy Object Editor". Right click on "Administrative Templates" under "User Configuration" -> All Tasks -> "Add/Remove Templates" -> Click on "Add" -> Select "Outlk11.ADM" and click "Open" -> Click "Close".
5. Expand "Microsoft Office Outlook 2003" under "Administrative Templates" -> Expand "Tools | Options" -> Expand "Preferences" -> Click on "Junk E-mail".
6. In the right pane double click on "Specify path to Safe Senders list".
7. Click on "Enabled" and under "Specify full path and filename to Safe Senders list" type UNC path of SafeSender.txt file (e.g.\\Server\JunkE-mail\SafeSenders.txt).
8. Double Click "Overwrite/Append Junk Email Import List" to configure if you want to keep user's own list.
9. Click on OK. Close "Group Policy Object Editor". Click OK again. Close Active Directory Users and Computers.
10. Log on to client machine and edit the following registry entry:
 
HKey_Current_User\Software\Microsoft\Office\11.0\Outlook\Options\Mail
DWORD = JunkMailImportLists
Value = 1
 
Note: This registry key should be deployed to the client machines for successfully deploying the Safe Senders List. We can use Group policy again to deploy this key. The value of this registry key will turn back to zero after Outlook applies the safe sender list from group policy. So if you need to modify the list, please change the value to 1 again.
 
11. Log off from the client machine and log on again.
12. Launch Outlook. Now you can see the email addresses in the Safe Sender list.
 
NOTE: The same procedure described above can be used to specify "Safe Recipients" and "Blocked Senders" list.
 
We also can use the Custom Installation Wizard or the Custom Maintenance Wizard to deploy such lists. Please refer to the following article for more information.

The problem now is,
I have export the regedit portion to junk.reg and include in the profile script and the system succesfully change the value from 0 to 1 in client computer. I tried to Enable this  "Overwrite/Append Junk Email Import List" to allow append but when I apply the setting it automatically change back to Disable..where to check for this to allow it Enable?

How To Create A Bootable USB Drive From Your Windows CD

http://www.intowindows.com/bootable-usb/

Windows Server 2008 Shortcut Keys

F5
Refresh the active window
F6
Cycle through screen elements in a window or on the desktop
F10
Activate the menu bar in the active program
ALT+F4
Closes the active item, or exit the active program
ALT+ESC
Cycle through items in the order in which they were opened
ALT+UP ARROW
View the folder one level up in Windows Explorer
ALT+TAB
Switch between open items
ALT+SPACEBAR
Open the shortcut menu for the active window
ALT+underlined letter
Perform the menu command (or other underlined command) and displays the corresponding menu
ALT+ENTER
Displays properties for the selected item
CTRL+Mouse scroll wheel
Change the size of icons on the desktop
CTRL+SHIFT+ESC
Opens Task Manager
CTRL+Windows logo key+F
Search for computers on the network
ESC
Cancels the current task
LEFT ARROW
Opens the next menu to the left, or close a submenu
RIGHT ARROW
Opens the next menu to the right, or open a submenu
SHIFT+F10
Displays the shortcut menu for the selected item
Windows logo key (or CTRL+ESC)
Open or closes the Start menu
Windows logo key+F4
Displays the Address bar list in Windows Explorer
Windows logo key+D
Displays the desktop
Windows logo key+E
Open Computer
Windows logo key+F
Searches for a file or folder
Windows logo key+L
Lock your computer or switch users
Windows logo key+M
Minimize all windows
Windows logo key+R
Opens the Run dialog box
Windows logo key+T
Cycle through programs on the taskbar
Windows logo key+U
Open the Ease of Access Center and choose accessibility features
Windows logo key+SHIFT+M
Restores minimized windows to the desktop
Windows logo key+PAUSE
Displays the System Properties dialog box

shortcut keys

1

Shortcut	Command	How useful(?)
CTRL combination shortcut keys Microsoft Excel 2007
CTRL+SHFT+(	Unhides any hidden rows within the selection.	+       –
CTRL+SHFT+)	Unhides any hidden columns within the selection.	+       –
CTRL+SHFT+&	Applies the outline border to the selected cells.	+       –
CTRL+SHFT_	Removes the outline border from the selected cells.	+       –
CTRL SHFT ~	Applies the General number format in Microsoft Excel.	+       –
CTRL+SHFT+$	Applies the Currency format with two decimal places (negative numbers in parentheses).	+       –
CTRL+SHFT+%	Applies the Percentage format with no decimal places.	+       –
CTRL+SHFT+^	Applies the Exponential number format with two decimal places.	+       –
CTRL+SHFT+#	Applies the Date format with the day, month, and year.	+       –
CTRL+SHFT+@	Applies the Time format with the hour and minute, and AM or PM.	+       –
CTRL+SHFT+!	Applies the Number format with two decimal places, thousands separator, and minus sign (-) for negative values.	+       –
CTRL+SHFT+*	Selects the current region around the active cell (the data area enclosed by blank rows and blank columns). In a PivotTable, it selects the entire PivotTable report.	+       –
CTRL+SHFT+:	Enters the current time.	+       –
CTRL+SHFT+	Copies the value from the cell above the active cell into the cell or the Formula Bar.	+       –
CTRL SHFT Plus ( )	Displays the Insert dialog box to insert blank cells in Microsoft Excel.	+       –
CTRL+Minus (-)	Displays the Delete dialog box to delete the selected cells.	+       –
CTRL+;	Enters the current date.	+       –
CTRL+`	Alternates between displaying cell values and displaying formulas in the worksheet.	+       –
CTRL+'	Copies a formula from the cell above the active cell into the cell or the Formula Bar.	+       –
CTRL+1	Displays the Format Cells dialog box.	+       –
CTRL+2	Applies or removes bold formatting.	+       –
CTRL+3	Applies or removes italic formatting.	+       –
CTRL 4	Applies or removes underlining in Microsoft Excel.	+       –
CTRL+5	Applies or removes strikethrough.	+       –
CTRL+6	Alternates between hiding objects, displaying objects, and displaying placeholders for objects.	+       –
CTRL+8	Displays or hides the outline symbols.	+       –
CTRL+9	Hides the selected rows.	+       –
CTRL 0	Hides the selected columns in Microsoft Excel.	+       –
CTRL+A	Selects the entire worksheet. If the worksheet contains data, CTRL+A selects the current region. Pressing CTRL+A a second time selects the current region and its summary rows. Pressing CTRL+A a third time selects the entire worksheet. When the insertion point is to the right of a function name in a formula, displays the Function Arguments dialog box. CTRL+SHFT+A inserts the argument names and parentheses when the insertion point is to the right of a function name in a formula.	+       –
CTRL+B	Applies or removes bold formatting.	+       –
CTRL+C	Copies the selected cells. CTRL+C followed by another CTRL+C displays the Clipboard.	+       –
CTRL+D	Uses the Fill Down command to copy the contents and format of the topmost cell of a selected range into the cells below.	+       –
CTRL+F	Displays the Find and Replace dialog box, with the Find tab selected. SHFT+F5 also displays this tab, while SHFT+F4 repeats the last Find action. CTRL+SHFT+F opens the Format Cells dialog box with the Font tab selected.	+       –
CTRL+G	Displays the Go To dialog box. F5 also displays this dialog box.	+       –
CTRL+H	Displays the Find and Replace dialog box, with the Replace tab selected.	+       –
CTRL I	Applies or removes italic formatting in Microsoft Excel.	+       –
CTRL+K	Displays the Insert Hyperlink dialog box for new hyperlinks or the Edit Hyperlink dialog box for selected existing hyperlinks.	+       –
CTRL+N	Creates a new, blank workbook.	+       –
CTRL O	Displays the Open dialog box to open or find a file. CTRL SHFT O selects all cells that contain comments in Microsoft Excel.	+       –
CTRL+P	Displays the Print dialog box. CTRL+SHFT+P opens the Format Cells dialog box with the Font tab selected.	+       –
CTRL+R	Uses the Fill Right command to copy the contents and format of the leftmost cell of a selected range into the cells to the right.	+       –
CTRL+S	Saves the active file with its current file name, location, and file format.	+       –
CTRL T	Displays the Create Table dialog box in Microsoft Excel.	+       –
CTRL+U	Applies or removes underlining. CTRL+SHFT+U switches between expanding and collapsing of the formula bar.	+       –
CTRL+V	Inserts the contents of the Clipboard at the insertion point and replaces any selection. Available only after you have cut or copied an object, text, or cell contents.	+       –
CTRL+W	Closes the selected workbook window.	+       –
CTRL+X	Cuts the selected cells.	+       –
CTRL Y	Repeats the last command or action, if possible in Microsoft Excel.	+       –
CTRL+Z	Uses the Undo command to reverse the last command or to delete the last entry that you typed. CTRL+SHFT+Z uses the Undo or Redo command to reverse or restore the last automatic correction when AutoCorrect Smart Tags are displayed.	+       –

Function keys Microsoft Excel 2007
F1	Displays the Microsoft Office Excel Help task pane. CTRL+F1 displays or hides the Ribbon, a component of the Microsoft Office Fluent user interface. ALT+F1 creates a chart of the data in the current range. ALT+SHFT+F1 inserts a new worksheet.	+       –
F2	Edits the active cell and positions the insertion point at the end of the cell contents. It also moves the insertion point into the Formula Bar when editing in a cell is turned off. SHFT+F2 adds or edits a cell comment. CTRL+F2 displays the Print Preview window.	+       –
F3	Displays the Paste Name dialog box. SHFT+F3 displays the Insert Function dialog box.	+       –
F4	Repeats the last command or action, if possible. CTRL+F4 closes the selected workbook window.	+       –
F5	Displays the Go To dialog box. CTRL F5 restores the window size of the selected workbook window in Microsoft Excel.	+       –
F6	Switches between the worksheet, Ribbon, task pane, and Zoom controls. In a worksheet that has been split (View menu, Manage This Window, Freeze Panes, Split Window command), F6 includes the split panes when switching between panes and the Ribbon area. SHFT+F6 switches between the worksheet, Zoom controls, task pane, and Ribbon. CTRL+F6 switches to the next workbook window when more than one workbook window is open.	+       –
F7	Displays the Spelling dialog box to check spelling in the active worksheet or selected range. CTRL+F7 performs the Move command on the workbook window when it is not maximized. Use the arrow keys to move the window, and when finished press ENTER, or ESC to cancel.	+       –
F8	Turns extend mode on or off. In extend mode, Extended Selection appears in the status line, and the arrow keys extend the selection. SHFT+F8 enables you to add a nonadjacent cell or range to a selection of cells by using the arrow keys. CTRL+F8 performs the Size command (on the Control menu for the workbook window) when a workbook is not maximized. ALT+F8 displays the Macro dialog box to create, run, edit, or delete a macro.	+       –
F9	Calculates all worksheets in all open workbooks. SHFT F9 calculates the active worksheet in Microsoft Excel. CTRL ALT F9 calculates all worksheets in all open workbooks, regardless of whether they have changed since the last calculation. CTRL ALT SHFT F9 rechecks dependent formulas, and then calculates all cells in all open workbooks, including cells not marked as needing to be calculated. CTRL F9 minimizes a workbook window to an icon.	+       –
F10	Turns key tips on or off. SHFT F10 displays the shortcut menu for a selected item in Microsoft Excel. ALT SHFT F10 displays the menu or message for a smart tag. If more than one smart tag is present, it switches to the next smart tag and displays its menu or message. CTRL F10 maximizes or restores the selected workbook window.	+       –
F11	Creates a chart of the data in the current range. SHFT+F11 inserts a new worksheet. ALT+F11 opens the Microsoft Visual Basic Editor, in which you can create a macro by using Visual Basic for Applications (VBA).	+       –
F12	Displays the Save As dialog box.	+       –

Other useful shortcut keys Microsoft Excel 2007
ARROW KEYS	Move one cell up, down, left, or right in a worksheet. CTRL+ARROW KEY moves to the edge of the current data region (data region: A range of cells that contains data and that is bounded by empty cells or datasheet borders.) in a worksheet. SHFT+ARROW KEY extends the selection of cells by one cell. CTRL+SHFT+ARROW KEY extends the selection of cells to the last nonblank cell in the same column or row as the active cell, or if the next cell is blank, extends the selection to the next nonblank cell	+       –
BACKSPACE	Deletes one character to the left in the Formula Bar in Microsoft Excel. Also clears the content of the active cell. In cell editing mode, it deletes the character to the left of the insertion point.	+       –
DELETE	Removes the cell contents (data and formulas) from selected cells without affecting cell formats or comments. In cell editing mode, it deletes the character to the right of the insertion point.	+       –
END	Moves to the cell in the lower-right corner of the window when SCROLL LOCK is turned on. Also selects the last command on the menu when a menu or submenu is visible. CTRL+END moves to the last cell on a worksheet, in the lowest used row of the rightmost used column. If the cursor is in the formula bar, CTRL+END moves the cursor to the end of the text. CTRL+SHFT+END extends the selection of cells to the last used cell on the worksheet (lower-right corner). If the cursor is in the formula bar, CT	+       –
ENTER	Completes a cell entry from the cell or the Formula Bar, and selects the cell below (by default). In a data form, it moves to the first field in the next record. Opens a selected menu (press F10 to activate the menu bar) or performs the action for a selected command. In a dialog box, it performs the action for the default command button in the dialog box (the button with the bold outline, often the OK button). ALT+ENTER starts a new line in the same cell. CTRL+ENTER fills the selected cell range	+       –
ESC	Cancels an entry in the cell or Formula Bar in Microsoft Excel. Closes an open menu or submenu, dialog box, or message window. It also closes full screen mode when this mode has been applied, and returns to normal screen mode to display the Ribbon and status bar again.	+       –
HOME	Moves to the beginning of a row in a worksheet. Moves to the cell in the upper-left corner of the window when SCROLL LOCK is turned on. Selects the first command on the menu when a menu or submenu is visible. CTRL+HOME moves to the beginning of a worksheet. CTRL+SHFT+HOME extends the selection of cells to the beginning of the worksheet.	+       –
PAGE DOWN	Moves one screen down in a worksheet. ALT+PAGE DOWN moves one screen to the right in a worksheet. CTRL+PAGE DOWN moves to the next sheet in a workbook. CTRL+SHFT+PAGE DOWN selects the current and next sheet in a workbook.	+       –
PAGE UP	Moves one screen up in a worksheet. ALT+PAGE UP moves one screen to the left in a worksheet. CTRL+PAGE UP moves to the previous sheet in a workbook. CTRL+SHFT+PAGE UP selects the current and previous sheet in a workbook.	+       –
SPACEBAR	In a dialog box, performs the action for the selected button, or selects or clears a check box. CTRL+SPACEBAR selects an entire column in a worksheet. SHFT+SPACEBAR selects an entire row in a worksheet. CTRL+SHFT+SPACEBAR selects the entire worksheet. If the worksheet contains data, CTRL+SHFT+SPACEBAR selects the current region. Pressing CTRL+SHFT+SPACEBAR a second time selects the current region and its summary rows. Pressing CTRL+SHFT+SPACEBAR a third time selects the entire worksheet. Wh	+       –
TAB	Moves one cell to the right in a worksheet. Moves between unlocked cells in a protected worksheet. Moves to the next option or option group in a dialog box. SHFT TAB moves to the previous cell in a worksheet or the previous option in a dialog box in Microsoft Excel. CTRL TAB switches to the next tab in dialog box. CTRL SHFT TAB switches to the previous tab in a dialog box.

AD Domains and Trusts	domain.msc
Active Directory Management	admgmt.msc
AD Sites and Services	dssite.msc
AD Users and Computers	dsa.msc
ADSI Edit	adsiedit.msc
Authorization manager	azman.msc
Certification Authority Management	certsrv.msc
Certificate Templates	certtmpl.msc
Cluster Administrator	cluadmin.exe
Computer Management	compmgmt.msc
Component Services	comexp.msc
Configure Your Server	cys.exe
Device Manager	devmgmt.msc
DHCP Management	dhcpmgmt.msc
Disk Defragmenter	dfrg.msc
Disk Manager	diskmgmt.msc
Distributed File System	dfsgui.msc
DNS Management	dnsmgmt.msc
Event Viewer	eventvwr.msc
Indexing Service Management	ciadv.msc
IP Address Manage	ipaddrmgmt.msc
Licensing Manager	llsmgr.exe
Local Certificates Management	certmgr.msc
Local Group Policy Editor	gpedit.msc
Local Security Settings Manager	secpol.msc
Local Users and Groups Manager	lusrmgr.msc
Network Load balancing	nlbmgr.exe
Performance Monitor	perfmon.msc
PKI Viewer	pkiview.msc
Public Key Management	pkmgmt.msc
QoS Control Management	acssnap.msc
Remote Desktops	tsmmc.msc
Remote Storage Administration	rsadmin.msc
Removable Storage	ntmsmgr.msc
Removable Storage Operator Requests	ntmsoprq.msc
Routing and Remote Access Manager	rrasmgmt.msc
Resultant Set of Policy	rsop.msc
Schema management	schmmgmt.msc
Services Management	services.msc
Shared Folders	fsmgmt.msc
SID Security Migration	sidwalk.msc
Telephony Management	tapimgmt.msc
Terminal Server Configuration	tscc.msc
Terminal Server Licensing	licmgr.exe
Terminal Server Manager	tsadmin.exe
UDDI Services Management	uddi.msc
Windows Management Instrumentation	wmimgmt.msc
WINS Server manager	winsmgmt.msc