Browsing "General"

Free Windows Live Messenger Invites!!

Yes I have some MSN Messenger Live invites to give out.

Want one?

Its easy, just leave a comment and explain why you prefer Windows over Unix.

I will pick the best replies and mail the invites out.

Good luck !

Jul 29, 2006 - General    No Comments

How can I force a net use command to remember the credentials to use for a server?

Ordinarily, you’re prompted for credentials when you access a remote server that’s outside of your regular account domain. However, if you use the /savecred switch with the net use command, it will prompt for the credentials to use and store the credentials for any future connection, as the following example shows:

net use * \savdaldc02temp /savecred

How can I burn a CD-ROM image from the command line?

The Windows Server 2003 and Windows XP resource kits provide the cdburn.exe utility, which, like the dvdburn.exe utility, can burn an ISO file to a physical CD burner drive and uses the format

cdburn <drive>: <image>

Typing cdburn with no parameters will list the utility’s Help information, which includes additional options related to the speed of the burn, type of write mode (e.g., session-at-once instead of the default track-at-once), and sector postgap options.

How can I migrate shares and their data between servers?

Microsoft provides the Microsoft File Server Migration Toolkit (FSMT), which you can download from Here . The tool lets you migrate shares and data from any server running Windows NT 4.0 or later to a Windows Server 2003 (or Windows Storage Server 2003) machine.

The utility also interfaces with DFS, which lets you maintain the original UNC path of the data and avoid complications with accessing data once it has been migrated. However, Windows Server 2003 Enterprise Edition lets you maintain the original UNC path, and if the old UNC path doesn’t need to be maintained, DFS isn’t required.

Mar 6, 2006 - General, Windows XP    No Comments

When you attempt to install Office 2003 on Windows XP, you receive ‘ERROR 1921′?

While installing Office 2003 on Windows XP, you receive a message similar to:

ERROR 1921
Service ‘MDM’ could not be stopped. Verify that you have sufficient privileges to stop system services.

This behavior occurs if the Machine Debug Manager service is not configured to start automatically.
To resolve this problem:

1. Open a CMD.EXE window.
2. Type the following command and press Enter:
REG ADD “HKLMSYSTEMCurrentControlSetServicesMDM /V Start /T REG_DWORD /F /D 2
3. Shutdown and restart Windows XP.
4. Install Office 2003.

Are there any registry keys or files that the account specified for a performance alert requires?

When you create a performance alert, by default it runs as the Network Service account. However, you can specify a different account for its execution. If you specify another account, ensure that the named account has the following rights:

* Read access to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionPerflib
* Full Access to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSysmonLog and its subkeys
* Read access to the files %windir%system32PERFC*.dat and %windir%system32PERFH*.dat

Dec 28, 2005 - Exchange, General, Windows 2003    No Comments

How do I remove my last Microsoft Exchange 5.5 Server installation from my Exchange Server 2003 organization?

Log on to the remaining Exchange 5.5 server and stop all services. The easiest way to do this is to stop the Exchange System Attendant by opening a command line and typing

net stop MSExchangeSA

You’ll see a warning that this command will stop other services, click Yes. After the command finishes running, run the command again (which will now stop the actual MSExchangeSA service).

# Log on to an Exchange 2003 server and start the Exchange 5.5 Administrator Console application (you must use the Exchange 5.5 version because Exchange 2003 tries to delete the Exchange server configuration from Active Directory–AD). Point the Exchange 5.5 Administrator Console to the Exchange 2003 server when prompted for a server.
# Expand the , Configuration, Servers node and select the Exchange 5.5 server in the right pane of the Exchange administration application. From the Edit menu select Delete. The application performs a check for resources; click Yes to any resources still found (assuming you know you’ve migrated everything you require). You might also see a warning that the MSFB and MS extensions could not be loaded. Click Ignore, then click OK to delete the confirmation message.
# Start the Exchange 2003 Exchange System Manager (ESM) and the Exchange 5.5 server will no longer be visible under the Servers container (, Administrative Groups, , Servers).
# You can now delete the Site Replication Service connection by opening the Tools, Site Replication Services node. Select the “Microsoft Exchange Site Replication Service ()” and select Delete from the Edit menu. Click Yes to the confirmation message.
# You can now raise the operational mode of the Exchange organization. Right-click the Exchange organization at the root of the node tree and select Properties. On the General tab click Change Mode, click Yes to the confirmation dialog box, then click OK to the main Properties dialog box
# Now you can remove the Active Directory Connector (ADC) connections. Start the Microsoft Management Console (MMC) Active Directory Connector Services snap-in. Right-click each connection under the Active Directory Connector node and select Delete. You might receive a warning that the connection is the primary connection agreement (CA). Click OK and click Yes to the delete confirmation dialog box (You’ll usually have at least two connections–one user and one public folder).
# You can now uninstall the ADC tools and services from the server.

Can I disable the Message Transfer Agent (MTA) on Microsoft Exchange Server 2003?

Microsoft has changed its stance about disabling the MTA on Exchange Server 2003. In Exchange 2000 Server, you couldn’t disable the MTA, but because of limitations with the MTA in cluster environments and because its primary use is for communicating with Exchange 5.5 servers, Exchange 2003 lets you disable the MTA.
The main problem with maintaining the MTA is that in a cluster, only one Exchange Virtual Server hosts the MTA resource, which is responsible for all mail transportation to Exchange 5.5 servers or third-party connectors for all databases hosted on the entire cluster. But the MTA can communicate with only 50 databases (60 with a change to the system; see the Microsoft article “How to increase the number of databases that are supported by the MTA service when Exchange Server 5.5 coexists with a server cluster that is running Exchange Server 2003″ here ). Because each node in a cluster can host 20 databases (five database over four storage groups), if you have more than three active nodes the MTA can’t communicate on behalf of all the databases in the cluster. For more information about disabling the MTA, see the Microsoft article “MTA Stacks service supportability guidelines for Exchange 2000 Server and Exchange Server 2003″ here
If you don’t require Exchange 5.5 communication or third-party connectors, and you want more than 60 databases in a cluster, you need to disable the MTA

Related Posts Plugin for WordPress, Blogger...