6 steps to restore SBS2003 to new server

Les (u da man) Connor’s six steps for moving SBS to a new server:


1. Install the loopback adapter(s) to hold the nic configuration(s).
2. Use ghost 2003 to image the existing server to a media that can be connected to the new server.
3. Move any hardware (if required) from old to new.
4. Restore the image onto the new server
5. If windows won’t start on new server, boot from SBS CD1 and run setup, selecting the repair option.
6. Transfer nic settings from loopbacks to nics.

Depending on whether WS2k3 has native drivers for all the hardware or not, you may need to have those available when you run setup. If it all goes pear shaped, you still have the old server – reverse the
changes you made in step 3 and step 1.


Les Connor
————————————-
SBS Rocks !

Ghost’ing an SBS Server

This information comes from Les!


I’ve yet to see ghost fail, and I’ve tested various scenarios with SBS. I suspect other imaging solutions will have similar success, but haven’t used anything other than ghost.

disk (scsi) to tape (dds)
disk (scis) to usb (1.1 and 2.0)
disk to disk (scsi to IDE)
disk to disk (scsi to scsi)

and done restores of each – both to the original hardware, and to drastically different hardware (which is the true test of complete disaster recovery, where the original server is gone).

There are a few issues, and they’ll vary by circumstance. For example:

a) sometimes Ghost has trouble picking up the tape drive, but persistence in trying a few different options on boot disks ususally results in success. Once you get a boot disk that works the way you want, duplicate and protect
it ;-).

b) usb 1.1 is a pita. It’s just way too slow, unless you can’t find another option. Using a usb 2.0 pci card is an option in some cases, but some servers (some dell’s for example) will not boot with a usb 2.0 pci card installed. Go figure. Dell says that’s the way it is, live with it. Ghost may not work with your usb 2.0 card – in some cases you have to disable the on-board usb 1.1 in order for ghost boot disk to find the 2.0 card.

c) You must be using the most recent ghost bits, or your Maxtor One-Touch USB drive will not be recognized. This info and the bits you need are on the symantec site.

d) When ghosting to different hardware, know how to handle the network configuration. If it’s a planned OS move, use the loop-back adapters (see http://www.smallbizserver.net/Default.aspx?tabid=99 for some tips). If it’s
not a planned move, as in disaster recovery, be prepared to deal with some nic issues, but they are resolveable. Just know that the issues will be there, and that help is available here.

e) In a move to different hardware, it is possible (perhaps even likely) that your box won’t boot to windows after the ghost restore. You can recover from this by booting from the SBS CD1, and when Setup determines that an OS
install exists – take the option to repair it. The setup is truly magic, I’ve not seen it fail.

f) even an out-dated ghost image is extremely handy; once the OS is recovered, you can restore newer files from your backup.

Symantec KB is not bad when it comes to resolving ghost issues.
If you’re new to Ghost, keep this link handy – http://ghost.radified.com/
truly a great resource for ghosters.


Les Connor
————————————-
SBS Rocks !

Setting workstation logoff/lockout time via Group Policy (GPO)

A commonly question asked is: can I automatically log off workstations after so many minutes of inactivity?


Well, through Group Policy you can force to lock down a workstation via a password protected screensaver, but not to log it off. The GPO settings for locking down a workstation via screensaver can be found at: 
Administrative templates\control panel\display\password protect the screen saver and screen saver timeout.


You can also use the WinExit.scr utility to implement the screen saver lockdown method. Check it out here:


http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techref/en-us/winexit.asp


Finally, there are third party vendors that may provide a solution to that problem.  One third party program is Fortress-NT/2000, available via the following link: http://www.whitehatinc.com/w2ktools/fortress/ .  The vendor claims that this program/utility can enforce log off times on client machines.  This is not a Microsoft product, and we cannot state how well, or if it does what it advertises to do.

Setting up a public resource calendar in Outlook/Exchange

Q: We are using a public calendar to reserve our conference room. We would like to be able to create an appointment
within our own calendar – invite the mail enabled calendar as a resource – and know that when we invite the calendar – it is not busy.

I have been able to accomplish all but one thing – showing the user if the conference room resource is busy when scheduling. The only thing it shows is “no information available”. How do I do that?


A: To set up a resource so that it can be scheduled requires using an Exchange mail account:  This procedure works only if you are the resource administrator or you’ve been given owner permissions.


http://office.microsoft.com/en-us/assistance/HP052516751033.aspx


  1. On the Tools menu, click Options, and then click Calendar Options.
  2. Click Resource Scheduling.
  3. Click the options you want.
  4. Click Set Permissions
  5. Click the Permissions tab, and then click Add.
  6. In the Type name or select from list box, enter the name of each person you want to grant permissions to, clicking Add after each name.
  7. Click OK.
  8. In the Permission Level list, click Author.