This is a document that explain the steps I took to migrate fax@vantage to a Windows 2003 Server. One of our client had outdated hardware that needed to be replace with a new server. When complete be sure to set the new server with the same name and IP address as the existing server.

Step 1 – Back up the Server

  • Copy the fax@vantage folder (C:\Program Files\Applied Systems\@vantage) from the existing server to a temp directory on the new server
  • Copy the database files (ASFaxingSQL.mdf and ASFaxingSQL_log.LDF) to the temp directory on the new server. To do this, browse to the utilities folder (the default location is C:\Program Files\Applied Systems\@vantage\utilities) and double click MSDEAdmin.exe
  • Enter Username: sa  and Password: Faxsupport03
  • Click Database Operations > Detach Database
  • Once complete navigate to C:\Program Files\Microsoft SQL Server\MSSQL$FAX\Data and copy ASFaxingSQL.mdf and ASFaxingSQL_log.LDF to a temp directory on the new server

Step 2 – Install Fax@vantage Software

Step 3 – Install and Configure the Brook Trout Fax Card

Do this first: http://www.appliedsystems.com/doc_central/BA-Business-App-Development/UninstallingBrooktroutDrivers.htm

then

Do this second: http://www.appliedsystems.com/doc_central/BA-Business-App-Development/InstallingBrooktroutTrufax200.htm

Step 4 – Copy the data from the temp directory to the Fax@vantage share

Step 5 – Move the Backup Database files to the correct directory and mount DB

Step 6 – Move the Archive folder to the D:\ if needed

Step 7 – Setup Auto-Logon for fax user account

See: http://support.microsoft.com/kb/324737

Step 8 – Test inbound and outbound

Prerequisite

  • Set up DRAC on new server and test access to new server from outside the firewall (need URL/credentials open port on firewall)
  • Make sure BESR Boot Disk is inserted in disk drive (option-create ISO of boot disk and mount)
  • Have the service tag or model number of new server to look up and download NIC and cotroller drivers
  • Available IP addess for new server during setup
  • NAS information for drive mapping
  • Setup maintainence/project window and notifacation to users

Step 1

  • Uninstall management software (if the server is a different brand)
  • Disble port 25 (Mail) and 4125 (RWW) on the firewall (disable not delete rule)
  • Download NIC and PERC RAID drivers of the new server to the desktop of the old server
  • Copy of the drivers on the NAS drive (Very Important)
  • Stop all scheduled Backup Exec Jobs
  • Disable Shadow Copy
  • Make a new BESR job set it to run to the NAS
  • Make sure restore anywhere is enabled (must be licensed to work)
  • Set to verify the image, make sure it starts properly

Step 2

  • Access new server via DRAC
  • Boot to the recovery CD on new server
  • Set an IP addess in BESR recovery CD menu
  • Map a drive to the NAS (use IP) in BESR recovery CD menu
  • Load driver for NIC and Controller
  • Deleted any additial drives such as recovery and FAT32 partitions
  • Load the image and start the restore process. We select the restore anywhere option, that will reset the HAL and all device drivers.
  • Repeat for D: if needed (size drive to remaining diskspace)
  • Reboot new server and enter BIOS to disabled NIC
  • Reboot and let windows redetect new Hardware and then it should automatically reboot
  • If we can get to the destop and then shut down server
  • Shutdown the old server
  • Reboot new server and enter BIOS to enable NIC
  • Set IP addess at the same IP address as the old server
  • Check services and event viewer
  • Activate Windows
  • Re-enable shadow copy
  • Resize the D: if needed (download and installed acronis disk director server 10.0 uninstall when complete)
  • Install NIC drives using the DRAC
  • Upated all Drivers and Firmware Chipset, BIOS if needed
  • Download and Install Dell Open Manage from support.dell.com
  • Enable Ports 25 and 4125 on firewall – verify port are open using canyouseeme.org
  • Appriver – release mail if needed

Verify:

  • Exchange -RDP client and test outlook
  • IIS (SharePoint,OWA, RWW,OM)
  • Server Administrator and Logs
  • Services/Event Viewer
  • Applications launch TAM
  • Create new BESR image of new sever

1. Click on Start, Run and type regedit.

  • Expand HKEY_LOCAL_MACHINE.
  • Click down the key path: “System\CurrentControlSet\Services\NtFrs\Parameters”
  • Double click on the value name  “Enable Journal Wrap Automatic Restore” and update the value.
  • If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

2.Restart File Replication Service services

3.Check event logs for repair ( may take a while so be patient)

4. download and install FRSDiag – http://www.microsoft.com/downloads/details.aspx?FamilyID=43CB658E-8553-4DE7-811A-562563EB5EBF&displaylang=en

5.Deleted registry key “Enable Journal Wrap Automatic Restore”If it does not restore correctly – http://support.microsoft.com/kb/316790

          I have been asked to roll out 29 new Dell Optiplex workstations and thought I would share my experience working with WDS. I will be installing Windows XP Professional SP2 on all workstation and the method of choice is to install WDS on the SBS 2003 server. I first verify the I had a server running Server 2003 SP2 and in my case I used Windows Small Business Server 2003 SP2.

Step 1 – Installing WDS on your Windows 2003 Server SP2

  • Logon to the Server with Domain Administrator rights 
  • Navigate to the control panel and click Add/Remove Programs
  • Click Add/Remove Windows Components
  • Scroll down and check Windows Deployment Services 
  • Click Next and Finish (once installed WDS can be found under Administrative Tasks)

Step 2 – Configure Windows Deployment Services

  • Navigate to Start > All Programs > Administrative Tools > Windows Deployment Services (WDS MMC should appear)
  • Expand Server and right click [sever name] and click Configure Server
  • Click Next to start the Wizard
  • Check the Path if needed (I used D:\Remoteinstall because of disk space on system drive C:)
  • For DHCP Options 60 Check both “Do not listen on Port 67” and “Configure DHCP option 60 to “PXE Client” and Click Next
  • For PXE Server Initial Settings select “Respond to all (known and unknown) client computers” and click Finish 

Step 3 – Download and Install Business Desktop Deployment 2007 (BDD 2007)

Step 4 – Install OS and all needed Applications (excluding Windows Media Player 11)

  • Enable network boot option in BIOS  
  • Install Operating System – In my case I installed a Volume Copy of Windows XP Professional SP2
  • Join to the Domain and install needed Application and Updates
  • Remove from Domain 

Step 5 – Setup Boot Image in WDS

  • Create a folder on the sever to copy two WIM files to (WinPE.WIM and Boot.WIM)
  • Insert a Vista Business DVD in to the DVD-ROM drive and browse the Disk for a file called Boot.WIM and copy to folder recently created folder
  • Navigate to Program Files\Windows AIK\Tools\PETools\x86\WinPE.WIM and Copy to recently created folder
  • Now I opened up WDS expanded Server and right clicked the Boot Image Folder and Clicked Add Image
  • Browsed to Boot.WIM  and click OK
  • Repeated for WinPE.WIM and click OK
  • Next, In WDS I right clicked WinPE and Clicked Capture Image
  • Finally, In WDS I created a Master Image Group called “Windows XP Image” 

Step 6 – Sysprep the Master Image

  • To Run the sysprep I inserted the XP Professional SP2 Disk and Browsed to the deploy.cab file (in my case it was D:\Support\Tools\Deploy.cab)
  • I used WinZip to extract the Deploy.cab file to a new folder I created called sysprep (C:\sysprep
  • Navigate to the C:\sysprep folder and launch setupmgr.exe
  • Click Next to Start the Wizard
  • Select “Create new” and click Next to continue
  • Select “Sysprep setup” and click Next to continue
  • Selct “Windows XP Professional” and click Next to continue 
  • Select “No,do not fully automate this installation” and click Next to continue
  • For Gernerl Settings enter the Name and Organization, Display Settings (default), enter the Time Zone applicable and then enter the Product Key
  • For Network Settings select “Automatically generate computer name, Select “Use the following Administrator password (127 characters maximum ; case-sensitive” and enter local administrator password and confirm. Select Typical settings and finally select Workgroup.
  •  For Advanced Settings specify Country or region, enter area code, Regional Settings select “Specify regional settings in the answerfile” and check “Customize the default regional settings” Click Custom and verify and enter sysprep Identification String (example Windows XP Deployment for Dell Optiplex 755 112007)
  • Click Finish and OK
  • Click Cancel to Close Setup Manager ( This is an annoying microsoft glitch)
  • Now runs Sysprep by navigating back to c:\sysprep and launch sysprep.exe
  • Click OK to Continue
  • The System Preparation Tool 2.0 windows should appear. Check “Use Mini-Setup and then Click Factory 
  • Once PC shuts down press the power button to restart the PC (PC will take some time to reboot)
  • Once at the Desktop Click Reseal and OK to Shutdown the PC
  • PC should Shutdown (do not boot to windows you need to PXE boot and capture the image
  • Sysprep is Complete 

Step 7 – Create Master Image for WDS

  • Boot up the PC that you want to image and press F12 to enter Boot Menu
  • Select Onboard Network Controller and press Enter
  • Press F12 again to Boot from network
  • Select Windows Vista PE (x86) and press Enter
  • From the command prompt type wdscapture.exe
  • Click Next to start the WDS Image Capture Wizard
  • In the Image Capture Source use the dropdown to select the volume to capture (in my case it was C:\) and enter an Image Name and Image Description. Once complete click Next
  • In the Image Capture Destination you will need to browse to a local Destination ( I had problems finding the WDS server when I checked “Upload image to WDS server:”)
  • Click Finish to begin capturing Image
  • Once I had the Image I restarted the Master-Image PC and Join to Domain
  • I copied the image file to a local directory on the WDS server
  • Once complete I opened WDS and expanded Servers> [Server Name] > Install Image
  • Right Click Install Image Group and Select  Add Install Image
  • Browse to the Image and Click OK to upload the Image to WDS

Step 8 – Image New PC

  • Press F2 to access the BIOS and make sure that PXEboot is enabled on the NIC
  • Press F12 to access the Boot Menu
  • Select “Onboard Network Controller
  • After DHCP issues IP address press F12 to continue
  • Select “Microsoft WindowsVista PE (x86)” and press Enter
  • Once wpeinit launches type the following:
    • Diskpart
    • Select disk 0
    • Clean
    • Exit
  • Type exit to let system restart
  • Press F12 and Boot from Onboard Network Controller
  • Press F12 to continue
  • Select “Microsoft Windows Longhorn setup (x86)” and press enter
  • Click Next to start the WDS wizard
  • Enter the domain administrator’s credentials and click OK
  • Highlight the Master Image and Click Next
  • Highlight Disk0 and Click Next – Installation will begin
  • After PC reboots the windows setup should appear click Next to begin
  • Select “Yes, I accept” to click Next
  • Enter the product Key and click Next
  • Enter Computer Name and click Next
  • Enter and confirm the local administrator password and click Next
  • Select No, don’t make this computer part of a domain and click Next
  • Click skip and slect No, not at this time and click Next
  • Click Finish
  • Once PC reboot confirm that you can logon to the desktop as a local administrator
  • Reboot in to the BIOS and disable Network PXE

Issues:

PROBLEM: Not able to configure WDS

CAUSE: REMINST.INF missing

RESOLUTION: Copied the same from service pack files folder

PROBLEM: Not able to PXE Boot to WDS – “WdsClient: An Error occurred while starting networking: a matching network card driver was not hound in this image. Please have your Administrator add the Network driver for this machine to the Windows PE image on the Windows Deployment Services server.” 

CAUSE: Boot Image missing network driver

RESOLUTION: Need to inject the network driver in the Windows PE image. I used the procedures at http://apcmag.com/5436/customise_windows_pe_2_0

      

PROBLEM: Reboot after loading the install image generates the corrupt hal.dll message ““Windows could not start because the following files is missing or corrupt: <Windows root>\systems32\hal.dll. Please re-install a copy of the above file.”

CAUSE: Hidden partition present and needed to delete

RESOLUTION: Resolution was added to procedures (see above)