Ultrasound: monitoring of Windows File Replication Service (FRS) 2000 and Windows Server 2003
As you know, the file replication service (FRS) is one of technologies of Windows 2000 and Windows Server 2003 for reply of the available data on share of network on more node.
It is a service that with the Windows Server 2003 R2 has been replaced by distributed file system (DFS), which improved and extended the functionality. But there are still many companies that using the file replication service, and for this I wanted highlight ultrasound, extremely useful to carry out the monitoring of francs, discover and resolve any problems of replica.
The new version of ultrasound adds the compatibility with Windows Server 2008.
You can download ultrasound for the monitoring of francs from here. If you install ultrasound on Windows Server 2008 64bit, you must first install hot fix KB 954737.
Two other tools that you can use with Windows Server 2003 and Windows 2000 for the monitoring of the replica of files, to combine with ultrasound, are frsdiag and sonar.
Frsdiag allows you the tools for troubleshooting the problem, while Sonar allows displaying graphic format in the state of replica.
I would highlight the resources of investigate on this topic:
- File Replication Service Diagnostics Tool (FRSDiag.exe)
- Sonar.exe: File Replication Service (FRS) Status Viewer
- TechNet Webcast: Migrating File Replication Service Replica Sets to Distributed File System Replication (Level 200)
- Monitoring and Troubleshooting the File Replication Service
- Windows Server 2003 File and Storage Services
- Webcast in Italiano: “Windows Server 2003 R2: migliorare la gestione dei dati aziendali con Distribuited File System”
Internet Information Services (IIS) 7.0 Manager
ADMX Migrator
Overview
You can select multiple ADM files for conversion. The ADMX Migrator creates a unique namespace which you can rename and will display a warning if a collision is detected due to duplicate names. Also, any items that cannot be validated against the ADMX schema are preserved in an Unsupported section. Please note that any annotations in ADM files are removed during the conversion process.
Additionally, the ADMX Migrator provides an ADMX editor with a graphical user interface for creating and editing Administrative Templates. You can select settings from menus rather than entering them manually in a text file, speeding template creation and reducing the chance for error.
Version 1.2 includes:
(1) Enhancements and bug fixes to support a wider range of ADM templates for conversion to ADMX.
(2) Enhancements to code and documentation for conversion error reporting and warnings.
(3) Improved handling of internationalized ADMX templates.
Download this Tool from Microsoft site
Office Communications Server 2007 Deployment Validation Tool
Overview
System Requirements
- Supported Operating Systems: Windows Server 2003; Windows XP Service Pack 2
- This download works with the following Office program:
- Microsoft Office Communications Server 2007
Instructions
- Download the file by clicking the Download button and saving the file to your hard disk.
- Double-click the program file on your hard disk to start the Setup program.
- Follow the instructions on the screen to complete the installation.
Instructions for use:
After you install this download, refer to the Microsoft Office Communications Server 2007 Deployment Validation Tool documentation for instructions.
To uninstall this download:
- On the Start menu, point to Settings and then click Control Panel.
- Double-click Add/Remove Programs.
- In the list of currently installed programs, select Microsoft Office Communications Server 2007 Deployment Validation Tool and then click Remove or Add/Remove. If a dialog box appears, follow the instructions to remove the program.
- Click Yes or OK to confirm that you want to remove the program.
VoIP test Set for Office Comunication Server 2007
Overview
- Client emulation - To emulate a Microsoft Office Communicator client, you specify a SIP-enabled user account to register with Office Communications Server. This can be useful for troubleshooting problems with incoming or outgoing Enterprise Voice calls. For example, an Office Communications Server engineer can use the tool in client emulation mode to quickly change user location profile information and validate that outbound routing is properly configured.
- Server emulation - You can use VoIP Test Set to emulate a Mediation Server or a gateway. To emulate a server, you specify the IP address, port number, and other settings of the server to be emulated. This can be useful for emulating components during the setup of the Office Communications Server 2007 infrastructure to verify the functionality of components that have already been deployed. For example, you might use the tool to receive and make calls directly from an IP/PSTN gateway to ensure that it is completely functional before deploying the complete Office Communications Server 2007 infrastructure.
How to rename a Windows 2000 domain
Pre-requisites
To successfully complete the procedures mentioned in the article, you need the following:
- Your domain must be in running in mixed mode. Once you have converted it to Native mode, you can’t revert back, and you can’t rename your domain.
- Since the domain is running in mixed mode, it must have at least one Windows NT 4.0 Backup Domain Controller (BDC). If you are running in mixed mode, but do not have an NT 4 BDC, then you need to install one for the purpose of renaming.
A word of caution
Although you can rename a Windows 2000 domain running in mixed mode, it is recommended that you decide well on the FQDN/DNS name of the domain well ahead of installation. Renaming, although possible, involves considerable amount of work and it can be avoided if proper planning is done before migrating to Windows 2000.
Before you attempt the procedure mentioned in this article, be sure to take a backup of all domain controllers involved in the process.
Overview
Major steps involved will be reverting Windows 2000 domain back to Windows NT (since NT domain names don’t have an FQDN name, they have only the NETBIOS name) then, upgrade to Windows 2000 and specifying a new FQDN name.
The steps below are specific for a scenario where there are no child domains (downgrade domain to NT 4, and upgrade domain to 2000). If you have child domain(s), then you have to downgrade the child domains back to NT 4 first, then downgrade the parent domain, upgrade the parent domain to Windows 2000 with the new FQDN, then finally upgrade the child domain to Windows 2000.
About the NetBIOS name
This article explains how to change the FQDN name or DNS name of the domain. The NETBIOS name will remain the same when NT4 domains are upgraded. If you need to change the NetBIOS name, you will need to setup a fresh domain with the new NetBIOS name and perform a full-blown migration from the existing domain to the new one. You may need to consider a whole lot of things before you do this. For example, other running server products like Exchange, custom applications that have the NetBIOS name hard-coded, etc.
Step 1. Inspect Windows NT 4.0 installation
1. If there is no existing Windows NT 4.0 BDC, you need to create one.
2. Make sure Service Pack 6 or 6a is installed.
3. To be double-sure, you can put up another BDC box and take it offline so that you have a copy of all your domain user accounts and SAM database in case something goes wrong. In such a case allow sufficient time for the BDC to gather all domain & security information. You can force a replication by using the command.
net accounts /sync
Step 2. Demote Windows 2000 domain controllers
1. If you have only one Windows 2000 domain controller, isolate it from the network. (remove the cables)
2. If you have more than one Windows 2000 domain controller, demote all except one Windows 2000 domain controllers by running DCPROMO. Isolate the last domain controller from the rest of the network (remove the cables).
3. After isolating the last domain controller, run DCPROMO and demote it. Be sure to choose “This is the last domain controller” option. (Note: DCPROMO requires an active network connection to continue, simply plug the domain controller into an ISOLATED active hub, or choose a bizarre IP address. The idea is to prevent the DC from talking to any other DC while running the DCPROMO demote)
Step 3. Promote Windows NT 4.0 BDC to a PDC
1. Now you have only Windows NT domain controllers. On the Windows NT 4 BDC, go to Server Manager and promote it to a BDC. You might get a message stating that it cannot contact the PDC. Choose Yes to continue. After the server restarts, make sure that it has become a PDC.
Step 4. Upgrade to Windows 2000
1. Upgrade this Windows NT 4.0 PDC to Windows 2000. When the installation completes, you will be asked to provide the FQDN. Provide the correct name that you desire.
2. Promote the other Windows 2000 DCs which you demoted earlier by using DCPROMO.
VSS update for Windows Server 2003
Install this update to improve the reliability, scalability, and memory optimization of the Volume Shadow Copy Service (VSS) in Windows Server 2003. After you install this item, you may have to restart your computer.
Update for Windows Server 2003 for Itanium-based Systems (KB940349)
Update for Windows Server 2003 32bit (KB940349)
Update for Windows Server 2003 x64 Edition (KB940349)
If you get more information about work with this service please go to link below:
Working with VSS services on Windows 2003 Server