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

• Additional Information: http://www.appliedsystems.com/doc_central/te-software-testing/4xwin2003migration.htm

Step 2 – Install Fax@vantage Software

• See: http://www.appliedsystems.com/doc_central/TE-Software-Testing/4x_Install4xFAXvantageCD.htm

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

http://support.microsoft.com/kb/832809

Step 1 – Download Adobe PDF IFilter 5.0 from the following Adobe Web site: http://www.adobe.com/support/downloads/detail.jsp?ftpID=1276 (http://www.adobe.com/support/downloads/detail.jsp?ftpID=1276) Step 2 - Stop the IIS Admin service. To do this, follow these steps:

Prerequisite

Step 1 – Set Sharepoint 2.0 to Companywebold

• Adding DNS entry so that companyebold resolved to the internal IP of SBS (Ping to verify name resolution)-Opened Sharepoint Central Administration (v2) and click the link to Configure Virtual Server Settings
• Select the companyweb virtual server, then click to Remove Windows SharePoint Services from virtual server
• Verify that the Remove without deleting content databases option is selected and clicked OK
• Opened IIS Manager, and open the Properties page for the companyweb web site
• Add two new host headers to the companyweb site – companywebold   and  companywebold.domain.local    Both host headers bound to port 80 on the internal IP of the SBS (not all unassigned).  DO NOT REMOVE the companyweb host headers at this point!
• Close the Properties pages of the companyweb site and returned to Sharepoint Central Administration (v2)
• Click on the Extend or Upgrade virtual server link, then clicked to extend the companyweb virtual server
• Click the option to Extend and Map to Another virtual server
• Verify that the companyweb site was being mapped, and that the option to Use an existing application pool is selected
• Verify that the DefaultAppPool was selected, then clicked OK
• Test SharePoint 2.0 works with http://companyweb and http://companywebold
• Open IIS Manager, expand [servername], expand [web sites], right-click on companyweb and select Properties-On the General tab, remove 444 from the SSL port, then click the Advanced button to edit the host headers-Remove two host headers: companyweb   and   companyweb.domain.local ,then clicked OK to close the companyweb properties page and close IIS ManagerStep 2 – Configure Companyweb to pull up SharePoint 3.0 site (Internal using port 80)
• Open SharePoint 3.0 Central Administration, and on the Application Management tab, Click on Create or extend Web application
• Click on Extend an existing web application
• Under Web application, Click Change web application then select WSS v3 web app (Sharepoint – 80)
• Under the IIS Web Site section, Select the option to Create a new IIS web site, and enter companyweb new for the description
• Enter 80 for the port, and  companyweb  for the host header, then clicked OK
• Verified that http://companyweb opened the new WSS v3 site

Step 3 – Configure Companyweb to pull up SharePoint 3.0 site (External using port 444)

Step 4 – Add SSL cert to External Virtual server

1. Click on Start, Run and type regedit.

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)

• Open a web browser and navigate to http://www.microsoft.com/downloads/details.aspx?FamilyId=13F05BE2-FD0E-4620-8CA6-1AAD6FC54741&displaylang=en 
• Save download locally to the server and install
• Once installed you will need to launch Workbench and added any required components 

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)

*Warning DO NOT upgrade existing WSS 2.0 site to WSS 3.0!! Install WSS 3.0 side by side**This is not supported by MicrosoftPrerequisites:

• Download WSS 3.0 http://www.microsoft.com/downloads/details.aspx?familyid=d51730b5-48fc-4ca2-b454-8dc2caf93951&displaylang=en
• Download Adobe PDF IFilter v6.0 http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611

Step 1 – Installation of Windows SharePoint Services 3.0

• After downloading WSS 3.0 launch SharePoint.exe-*Select “No, do not upgrade at this time
• Click on the “Data Location” Tab (click “Browse” to select the location of the data)
• Click Install Now
• When complete make sure the “Run the SharePoint Products and Technologies Configuration Wizard now” is checked and click Close
• Click Next and accept the Service Restart warning message and let it finish all 10 tasks
• Click Finish

Step 2 – Change the new site to resolve “intranet” during transition

• Add a hostname in DNS with the name Intranet and the IP of the SBS (ping intranet to confirm name resolution)
• Open SharePoint 3.0 Central Administration, and click on the Application Management tab.
• Under the SharePoint Web Application Management section, click on Create or extend Web application.
• Click to Extend existing web application.
• On the page that opens, click on the Web Application field and select Change Web Application. 
• On the page that opens, select your SharePoint Web Application. 
• In the IIS Web Site section, select the option to create a new web site.
• Enter a description for the new site (e.g.  Intranet)
• In the Port field, enter 80
• In the Host Header field, enter   intranet
• Click OK.
• Verify that http://intranetopens/opens the new SharePoint Site-Return to the SharePoint 3.0 Central Administration and click on the Application Management tab.
• Under the SharePoint Web Application Management section, click on Remove SharePoint from IIS WebSite-In the Web Application section, verify that the web application is http://servername
• In the Deletion Options section, verify that the IIS Website is set to SharePoint – 80 (Default)
• Select the option to Delete IIS Web sites-Click OK
• Open IIS Manager, expand [servername] and expand web sites.  Select the default web site and click the Start button