Reset the DSRM Administrator Password

Prior to Windows 2003 SP1 the DSRM (Directory Services Restore Mode) password was automatically synchronised with the Domain Administrator account password whenever you changed the domain admin account. With Win2003 SP1 and the breaking of this functionality you will find the below error in your application event log if these two passwords don’t match.

Event Type:    Error

Event Source:    dsrestor
Event Category:    None
Event ID:    1005
Date:        8/03/2009
Time:        2:31:19 PM
User:        N/A
Computer:    XXXXXXXXX
Description:
The DSRestore Filter failed to connect to local SAM server. Error returned is <id:997>.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
You can safely ignore this error if you know what your DSRM Password is and want to keep them the same across different domain controllers in different domains otherwise you can follow the steps below to change DSRM Password to match the domain administrator account.

To Reset the DSRM Administrator Password

1. Click, Start, click Run, type ntdsutil, and then click OK.
2. At the Ntdsutil command prompt, type set dsrm password.
3. At the DSRM command prompt, type one of the following lines:
   • To reset the password on the server on which you are working, type reset password on server null. The null variable assumes that the DSRM password is being reset on the local computer. Type the new password when you are prompted. Note that no characters appear while you type the password.

     -or-

   • To reset the password for another server, type reset password on server servername, where servername is the DNS name for the server on which you are resetting the DSRM password. Type the new password when you are prompted. Note that no characters appear while you type the password.
4. At the DSRM command prompt, type q.
5. At the Ntdsutil command prompt, type q to exit.

Open MYOB Datafile automatically

Technically this can be use used to have any program open up a file it can understand when its run. But you would generally associate a file extension with a particular program and just double click on the file itself.

The reason I’m using this method for MYOB is that sometimes when MYOB gets upgraded and you try and re-associate the myo extension with the new program windows does not actually do it and continues to try and open the files with the lower version of MYOB. I suspect this has something to do with the program itself having the same name just with a different path but I’ve not troubleshooted it as the below works around the problem easy enough.

All you need to do is create a new shortcut to the MYOB executable (or edit the one on your desktop) and then place the full path to the *.myo file after it in the target field.

As shown below the path to the command would be c:\Premier12\Myobp.exe “C:\Your Path\Company File.myo”

Click Ok and now you can just double click on your shortcut and have the correct version of MYOB open up the datafile.