Ramblings From The Litter Tray of Life

Posts Tagged ‘registry’

How to repoint Veritas Replication Exec console

Posted by graycat on 5 December 2008

Sometimes you’ve just got to move an application to another server. It’s just the way it goes. Unfortunately quite often that means you’ve got to remove / reinstall all the clients …. which can be a pain.

We recently had to migrate the “master server” (otherwise known as the RMS server) for replication exec and change the Replication Neighborhood at the same time. Personally, I really didn’t want to reinstall the console on numerous PC’s and servers so I found the registry keys that do the pointing.

To change the RMS server, alter: HKLM\SOFTWARE\VERITAS\ENL\Network.TCPIP\gateway to the new server name or IP address. You’ll have to restart the Veritas service for this to kick in but it’s a 2 second job.

To change the Replication Neighborhood go to KLM\SOFTWARE\VERITAS\ENL\System\netgroup and alter that to the new name. No service restart required for this one.

Job done.

Advertisements

Posted in Applications, IT | Tagged: , , , , , , | Leave a Comment »

WSUS in the Workgroup

Posted by graycat on 27 August 2008

Sometimes you might be needing an update server in a small company or network where there is no domain or, like me in this case, you’re building a new machine and need to update it without joining it to the domain. Now even if you install the OS using the latest repository from the manufacturer you are going to have to update it further. This updating can take ages when pulled over the inter-web from MS so accessing a WSUS server would be ideal.

Well with a little work, you can get a workgroup machine to use your domain WSUS server ….. and here’s how.

Two main options really (as laid out here by Microsoft) – policy based and registry based. I’m not going to go into the policy based stuff as that’s really well covered in the MS page and very straight forward. The method I’ve just used though is adding to the registry.

After a little searching I ran across a few reg keys that’ll point the machine towards the right WSUS, set download / install options and even drop it into the right WSUS group. In the end I went with this reg settings:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\]
“WUServer”=”http://192.168.0.100”
“WUStatusServer”=”http://192.168.0.100”

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\]
“AUOptions”=dword:00000002
“NoAutoRebootWithLoggedOnUsers”=dword:00000001
“NoAutoUpdate”=dword:00000000
“RescheduleWaitTime”=dword:00000005
“ScheduledInstallDay”=dword:00000000
“ScheduledInstallTime”=dword:00000000
“UseWUServer”=dword:00000001

The first few keys are pretty self evident as specifying your WSUS server. I’ve seen people suggesting that the server name, FQDN and IP address all work but I could only get the IP address to work and think this is a better solution anyway. In these keys you will also need to specify the port number to use if it is not the default port 80. This is done thus “http://192.168.0.100:8530”.

The AU section is where it gets interesting and allows you to set all the options such as downloading, installing and reboots. The AUOptions dword options go like this:

  • 1 – Keep my computer up to date has been disabled in Automatic Updates.
  • 2 – Notify of download and installation.
  • 3 – Automatically download and notify of installation.
  • 4 – Automatically download and scheduled installation.

Personally I’m an option 3 kinda guy when it comes to servers, ie: download it but I’ll give final approval to install it or not manually. Yes, this takes more time but it’ll save a lot more time if something goes wrong IMO.

The other keys are pretty easy to follow so I won’t rewrite the MS article but here’s an overview.

ScheduledInstallDay – which days to install on. 0 = everyday

ScheduledInstallTime -what time you want the install to run using 0 – 23 time format (for the hours if you’re not hip with the military speak)

NoAutoUpdate – enables or disables autoupdate.

NoAutoRebootWithLoggedOnUsers – true or false situation. If set to 1, will not automatically restart a computer while users are logged on.

Posted in IT | Tagged: , , , | Leave a Comment »

Where’s my MSCONFIG gone?!

Posted by graycat on 24 June 2008

[dodgey sci-fi voice over]

There exists and application.

So powerful that it keeps the load-up in line.

It has existed since the dawn of XP.

But now it has …… gone!

[/dodgey voice over]

Ok, it’s nothing quite that amazing or worthy of it’s own show with a special effects budget but it is very useful.

MSCONFIG is an application in Windows XP that is used to troubleshoot the start-up process of a machine. With it you can see what is starting up when, what applications are launching in the background, what services are set to start or not and a few other things.

The most common use I’ve seen for it is to simply speed up the boot process by cutting down what is launched in the background.

When you launch this from the command line (type msonfig and hit go) you’ll be presented with a number of tabs. These are:

  • General – gives you options on what mode to start Windows in (safe mode etc)
  • System.ini – is where old versions of Windows lists system files to be loaded, such as drivers and fonts
  • Win.ini – is pretty much redundant nowadays but pertains to old versions of Windows
  • Boot.ini – provides some extra boot options
  • Services – controls the services
  • Startup – deals with what applications are launched at start-up.

There’s also a “Tools” tab but that’s only in Vista so I’m not going to cover it here. Oh, whilst msconfig is native in XP, you can copy it over to a 2000 Pro machine and it’ll run fine from there. handy if you’ve got a mixed environment.

Now more often than not this little app is just there and saves a lot of time and effort. However, on the odd occasion simply typing msconfig in the run box will produce the dreaded “command not recognised” error message.

But worry not! It is still there, it’s just not been registered. To quickly find it you need to go to “c:\windows\pchealth\helpctr\binaries” and low, you will find what you seek.

Personally, if a machine slides sufficiently that I need to use msconfig and its not there then it instantly jumps up the queue for being rebuilt ala the ghosting process. However, if that’s not possible and you want to fix it so you can just type msconfig at the root command line you can correct the issue in the registry. The path declared under HKLM\sotware\microsoft\windows\currentversion\app paths\msconfig\

Posted in Applications, IT | Tagged: , , | Leave a Comment »