Guest Rayees Posted August 20, 2007 Posted August 20, 2007 Dear All I was trying to use ASR in my enviroment. I could also successfully complete the process of both Backup and restore without any issue. However I would like to fine tune little more, I was reading certain microsoft article where it said that you can automate the ASR restore process through RIS. I'm already using WDS at my environment, I would like to know how to make use of RIS/WDS to automate the restore process of ASR. I'm unable to find any knowledbase article for the same, request your help/guidance to move forward. Thanks in advance With kind Regards Rayees
Guest Mike Luo [MSFT] Posted August 21, 2007 Posted August 21, 2007 RE: How to automate ASR restore process Hello, Thank you for using newsgroup! I didn't completely understand the mean "how to make use of RIS/WDS to automate the restore process of ASR". Could you explain me for more detail? Thanks & Regards, Mike Luo Microsoft Online Partner Support Get Secure! - http://www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Guest Rayees Posted August 21, 2007 Posted August 21, 2007 Re: How to automate ASR restore process HI Mike, let me explain where I got stuck At present I'm taking ASR backup of my servers manually, as you aware while creating ASR I also create floppy for each server and maintain those floppies separately. When there is a need to restore ASR, I use the floppy which I created during backup and restore the server by pointing to the .bkf file which I created during backup. It works fine no problem in this. Now the issue is, I have few hundred servers. Doing the above mentioned steps manually is a difficult task for me. Hence I thought of automating the "Restore" process. I went through lot of microsoft article and I happen to read a Microsoft article by name "How ASR Works" where in this document I read these lines "You normally access the ASR state file (Asr.sif) through a local floppy disk drive. If the computer does not have a floppy disk drive, or you want to perform an ASR restore over a network or remotely, you can use a Remote Installation Services (RIS) server to fully automate the ASR process." In my environment I already have Windows Deployment Services (WDS) (WDS is a upgrade of RIS). So I would like to know how make use of RIS to automate ASR. Hope I clarified my point Regards Rayees "Mike Luo [MSFT]" <v-miluo@online.microsoft.com> wrote in message news:fshSDy84HHA.2340@TK2MSFTNGHUB02.phx.gbl... > Hello, > > Thank you for using newsgroup! > > I didn't completely understand the mean "how to make use of RIS/WDS to > automate the restore process of ASR". Could you explain me for more > detail? > > Thanks & Regards, > > Mike Luo > > Microsoft Online Partner Support > Get Secure! - http://www.microsoft.com/security > > ===================================================== > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. >
Guest Rayees Posted August 23, 2007 Posted August 23, 2007 Re: How to automate ASR restore process Can any one help me please........... With kind Regards Rayees. "Rayees" <rayees@newsgroup.nospam> wrote in message news:uIsIZG%234HHA.484@TK2MSFTNGP06.phx.gbl... > HI Mike, let me explain where I got stuck > > At present I'm taking ASR backup of my servers manually, as you aware > while creating ASR I also create floppy for each server and maintain those > floppies separately. When there is a need to restore ASR, I use the > floppy which I created during backup and restore the server by pointing to > the .bkf file which I created during backup. It works fine no problem in > this. > > Now the issue is, I have few hundred servers. Doing the above mentioned > steps manually is a difficult task for me. Hence I thought of automating > the "Restore" process. I went through lot of microsoft article and I > happen to read a Microsoft article by name "How ASR Works" where in this > document I read these lines "You normally access the ASR state file > (Asr.sif) through a local floppy disk drive. If the computer does not have > a floppy disk drive, or you want to perform an ASR restore over a network > or remotely, you can use a Remote Installation Services (RIS) server to > fully automate the ASR process." > > In my environment I already have Windows Deployment Services (WDS) (WDS is > a upgrade of RIS). So I would like to know how make use of RIS to > automate ASR. > > Hope I clarified my point > > Regards > Rayees > > > "Mike Luo [MSFT]" <v-miluo@online.microsoft.com> wrote in message > news:fshSDy84HHA.2340@TK2MSFTNGHUB02.phx.gbl... >> Hello, >> >> Thank you for using newsgroup! >> >> I didn't completely understand the mean "how to make use of RIS/WDS to >> automate the restore process of ASR". Could you explain me for more >> detail? >> >> Thanks & Regards, >> >> Mike Luo >> >> Microsoft Online Partner Support >> Get Secure! - http://www.microsoft.com/security >> >> ===================================================== >> When responding to posts, please "Reply to Group" via your newsreader so >> that others may learn and benefit from your issue. >> ===================================================== >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> > >
Guest Mike Luo [MSFT] Posted August 23, 2007 Posted August 23, 2007 Re: How to automate ASR restore process Hello, You may follow these steps: Setting up the RIS server to use ASR 1. Set up the RIS server to support automation of the F12 PXE boot that executes the ASR restore option. To do this, follow these steps: a. Verify the BIOS boot order on the RIS server and on each of the client computers. Position the hard disk first in the boot order, and then position the PXE option second in the boot order. b. Rename the current Startrom.com file as Startrom.bak (for backup purposes). This file is located in the \\RISserver\Reminst\OSChooser\I386 folder on the RIS server, c. Rename the Startrom.n12 file as Startrom.com. This file is located in the \\RISserver\Reminst\OSChooser\I386 folder on the RIS server. The new version of Startrom.com automates the process when the user presses F12 to prompt Trivial File Transfer Protocol (TFTP) for the initial download. 2. Make backups of the following files, and then rename them in the \\RISserver\Reminst\OSChooser\Language folder: ? Rename Welcome.osc as Welcome.bak. ? Rename Login.osc as Login.bak. ? Rename Install.osc as Install.bak. ? Rename Warning.osc as Warning.bak. Note As a best practice, make a backup copy of each .osc file before you make any changes in the \\RISserver\Reminst\OSChooser\Language folder. 3. Edit the following .osc files on the RIS server: a. Welcome.osc <OSCML> <META KEY=ENTER HREF="LOGIN"> <META KEY=F3 ACTION="REBOOT"> <META KEY=ESC HREF="LOGIN"> <META KEY=F1 HREF="LOGIN"> <TITLE> Client Installation Wizard Welcome</TITLE> <FOOTER> [ENTER] continue </FOOTER> <META ACTION=AUTOENTER> <BODY left=5 right=75> Welcome to the Client Installation Wizard. This Wizard helps you quickly and easily set up a new operating system on your computer. You can also use this Wizard to keep your computer up-to-date and to troubleshoot computer hardware problems. In the Wizard, you are prompted to use a valid user name, password, and domain name to log on to the network. If you do not have this information, contact your network administrator before continuing. </BODY> </OSCML> Copy this code to the \\RISserver\Reminst\OSChooser folder, and then save the file as Welcome.osc. After you add "META ACTION=AUTOENTER" to this code, the user does not have to press ENTER in the Client Installation Wizard because this action is automated. b. Login.osc <OSCML> <TITLE> Client Installation Wizard Logon</TITLE> <FOOTER> [ENTER] continue [ESC] clear [F1] help [F3] restart computer</FOOTER> <META KEY=F3 ACTION="REBOOT"> <META KEY=F1 HREF="LOGINHLP"> <META KEY=ESC HREF="LOGIN"> <META ACTION="LOGIN"> <META ACTION=AUTOENTER> <BODY left=5 right=75> Type a valid user name, password, and domain name. You may use the Internet-style logon format (for example: someone@example.com). <FORM ACTION="CHOICE">   User name: <INPUT NAME="USERNAME" MAXLENGTH=255 TYPE=TEXT VALUE=*****>    Password: <INPUT NAME="*PASSWORD" TYPE=PASSWORD MAXLENGTH=20 VALUE=*****> Domain name: <INPUT NAME="USERDOMAIN" VALUE=%SERVERDOMAIN% MAXLENGTH=255> </FORM> Press the TAB key to move between the User name, Password, and Domain name fields. You are connected to %SERVERNAME% </BODY> </OSCML> Copy this code to the \\RISserver\Reminst\OSChooser\Language folder, and then save the file as Login.osc. The two values that you must add to the Login.osc file instead of ***** are the user name and the password for the client. For example, if your user name is "ristest" and your password is "deploy," these two lines will appear as follows:   User name: <INPUT NAME="USERNAME" MAXLENGTH=255 TYPE=TEXT VALUE=ristest>    Password: <INPUT NAME="*PASSWORD" TYPE=PASSWORD MAXLENGTH=20 VALUE=deploy><BR> Note If you do not prestage computers in your environment, the user name that you create for RIS must have both of the following permissions: ? Read ? Create Computer Objects c. Install.osc <OSCML> <META KEY=ESC ACTION="REBOOT"> <META KEY=ENTER ACTION="REBOOT"> <META ACTION=AUTOENTER> <TITLE> Client Installation Wizard Installation Information</TITLE> <FOOTER> [ENTER] continue</FOOTER> <BODY left=5 right=75> The following settings will be applied to this computer installation. Verify these settings before continuing. Computer account: %MACHINENAME% Global Unique ID: %GUID% Server supporting this computer: %SERVERNAME% To begin Setup, press ENTER. If you are using the Remote Installation Services boot floppy, remove the floppy disk from the drive and press ENTER to continue. </BODY> </OSCML> Copy this code to the \\RISserver\Reminst\OSChooser\Language folder, and then save the file as Install.osc. When you add "META ACTION=AUTOENTER" to this code, the user does not have to press ENTER in the Client Installation Wizard because this action is automated. d. Warning.osc <OSCML> <META KEY=ENTER HREF="INSTALL"> <META KEY=ESC HREF="CHOICE"> <META KEY=F3 ACTION="REBOOT"> <META SERVER ACTION="WARNING"> <META ACTION=AUTOENTER> <TITLE> Client Installation Wizard Caution</TITLE> <FOOTER> [ENTER] continue [ESC] cancel [F3] restart computer</FOOTER> <BODY left=5 right=75> <FLASH> <PRE> * * * C A U T I O N * * * </PRE> </FLASH> <BOLD> <PRE> All data on the hard drive will be deleted! </PRE> </BOLD> Before the new operating system is installed, this computer's hard drive must be repartitioned and formatted. All existing data on the drive will be deleted during this process. To continue, press ENTER. To cancel the installation, press ESC. </BODY> </OSCML> Copy this code to the \\RISserver\Reminst\OSChooser\Language folder, and then save the file as Warning.osc. When you add "META ACTION=AUTOENTER" to this code, the user does not have to press ENTER in the Client Installation Wizard because this action is automated. 4. Set the Group Policy to allow only automatic RIS setup installations. To do this, follow these steps: a. Click Start, point to All Programs, point to Administrative Tools, and then click Active Directory Users and Computers. b. Right-click your domain or the organizational unit where the policy that you want to edit is applied, and then click Properties. c. Click the Group Policy tab. d. Click Default Domain Policy, and then click Edit. e. In the left pane, expand User Configuration, and then expand Windows Settings. f. Click Remote Installation Services. g. In the right pane, double-click Choice Options. h. In the Choice Options Properties dialog box, select the following options: ? Under Automatic Setup, click Disabled . ? Under Custom Setup, click Disabled . ? Under Restart Setup, click Disabled . ? Under Tools, click Enabled . Then click OK. i. Close the Group Policy Object Editor, and then click OK in the Properties box for your domain. Creating an ASR backup set To create an ASR backup that is set to a tape backup or to create an ASR backup that is set to the \\RISserver\Reminst\Setup\English\Images\ ASRImageName folder as Asr.bkf by using the Backup utility in Windows Server 2003, follow these steps: 1. Create a new Windows Server 2003 CD-based image on the RIS server, and name the image folder the same as the corresponding computer name. 2. On the computer that performs the ASR backup, map network drive Z to the folder on the RIS server that contains the image that you created. When you restore the image with ASR later, it automatically locates the correct files from the Asr.sif file and the Mapdrv.cmd file on network drive Z. For example, map the \\RISserver\Reminst\Setup\English\Images\ ASRImageName folder to network drive Z on the computer where the ASR backup is performed. 3. Click Start, point to All Programs, point to Accessories, and then click Backup. 4. To create an ASR backup set in the Backup or Restore Wizard, do one of the following Note By default, the Backup or Restore Wizard starts, unless it is disabled. a. To create an ASR backup set in the Backup or Restore Wizard, click to select All information on this computer in the What do you want to backup? area. b. If the Backup or Restore Wizard is disabled, create an ASR set in Advanced Mode. In the Backup Utility dialog box, click ASR Wizard on the Tools menu, and then follow the instructions that appear on your screen. Installing the new build image on the RIS server Note You must first create a CD-based image of the operating system that you want to use for ASR. In all cases with RIS images, you must create a CD-based image that provides backup files for subsequent RIPrep, ASR, or WinPE images that you might create. Therefore, for every operating system that you use for ASR, RIPrep, or WinPE images, you must have a CD-based image that corresponds to the binary version of that operating system. For example, you might need an image that corresponds to Windows Server 2003, Windows Server 2003 Service Pack 1, and so on. To install the new build image on the RIS server, follow these steps: 1. Click Start, and then click Run. 2. Type risetup.exe , click OK, and then follow the steps to complete the wizard. Note If this is a clean install of the volume that contains the build images, set the Tool.osc file so that the Tools image (Tools.osc) can be selected automatically. This can be done in either of the following two ways: a. If there is only one Tools image on the RIS server, remove the "NOAUTO" text from the default Tools.osc file. b. If there is more than one Tools image, leave the "NOAUTO" text unchanged . The following OSCML section from the default Tools.osc file shows where the "NOAUTO" text is located: <OSCML> <META KEY=F3 ACTION="REBOOT"> <META KEY=F1 HREF="TOOLSHLP"> <META KEY=ESC HREF="CHOICE"> <META SERVER ACTION="ENUM TOOLS CMDCONS"> <TITLE> Client Installation Wizard Tools</TITLE> <FOOTER> [ENTER] continue [ESC] go back [F1] help [F3] restart computer</FOOTER> <BODY left=5 right=75> <BR> <BR> Use the arrow keys to select one of the following options: <BR> <P left=8> <FORM ACTION="LAUNCH"> <SELECT NAME="SIF" NOAUTO SIZE=12> %OPTIONS% </SELECT> </FORM> </P> <BOLD>Description:</BOLD>   <TIPAREA> </BODY> </OSCML> If this is not a clean install of the volume that contains the build images or if the Tool.osc file has been modified, you must select the Select old menu screens option during RIS setup to make sure that the Tool.osc file is not overwritten. 3. Copy the build image to a new name in the current folder. The name of the new image folder is not important, but it will be used to identify where bits are copied in the future. For example, the first image is located in E:\RemoteInstall\Setup\English\Images\Win.Net¨CADS, and the copied image is located in E:\RemoteInstall\Setup\English\Images\ ASRComputerName BK-ADS. Note When you copy the CD-based image, you do not want to modify the image that is required for the backup files. Therefore, you must copy the CD-based image into a new folder and use the following naming convention to rename the image: ASR ComputerName operating_system_version ASR indicates that this image is used for an ASR. ComputerName identifies the exact computer that this ASR backup/disaster recovery image belongs to. (Because ASR images are computer-specific, the images can only be used for the computer installation that they were originally created from). OSVer specifies the operating system version for this image. 4. Update the Ristndrd.sif file that is located in the \\RISserver\Reminst\Setup\English\Images\ASR ComputerName-OSVer \i386\Templates folder so that the copied image supports ASR, and then rename the file Asr.sif. Do not confuse this Asr.sif file with the actual Asr.sif file that the Windows Server 2003 Backup utility generates. Note Modify the Ristndrd.sif answer file in the newly created ASR ComputerName-OSVer image folder, not in the CD-based image folder that you originally created by using the Risetup.exe tool and copied from. The following sample Asr.sif file contains the specific changes that you must make to the [OSChooser] section to support a Tools (ASR) image: [data] floppyless = "1" msdosinitiated = "1" OriSrc = "\\%SERVERNAME%\RemoteInstall\%INSTALLPATH%\%MACHINETYPE%" OriTyp = "4" LocalSourceOnCD = 1 [setupData] OsLoadOptions = "/noguiboot /fastdetect" SetupSourceDevice = "\Device\LanmanRedirector\%SERVERNAME%\RemoteInstall\%INSTALLPATH%" [unattended] OemPreinstall = no FileSystem = LeaveAlone ExtendOEMPartition = 0 TargetPath = \WINDOWS OemSkipEula = yes InstallFilesPath = "\\%SERVERNAME%\RemoteInstall\%INSTALLPATH%\%MACHINETYPE%" LegacyNIC = 1 [userData] FullName = "Microsoft Corporation" OrgName = "Microsoft Corporation" ComputerName = %MACHINENAME% ProductID = "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" [GuiUnattended] OemSkipWelcome = 1 OemSkipRegional = 1 AdminPassword = "Storage12" AutoLogon = yes AutoLogonCount = 1000 TimeZone = 4 [LicenseFilePrintData] AutoMode = PerSeat [GuiRunOnce] [Display] BitsPerPel = 16 XResolution = 800 YResolution = 600 VRefresh = 60 [Networking] [NetServices] MS_Server=params.MS_PSched [identification] JoinDomain = %MACHINEDOMAIN% DoOldStyleDomainJoin = Yes [RemoteInstall] Repartition = yes UseWholeDisk = yes [OSChooser] ASRFile=asrpnpfiles\%guid%.sif ASRINFFile=\Device\LanmanRedirector\%SERVERNAME%\RemoteInstall\ASRFiles\%gui d%.sif Description ="ASRMachineName-2003-ADS(Backup-Date)" Help ="This image Restores and ASR backup image of Operating System for Dated date " LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" ImageType = "ASR" Version="5.1 (0)" [Components] ;ApplicationServer = OFF ;iis_common = ON ;iis_inetmgr = ON ;iis_pwmgr = ON ;iis_www = ON ;iis_ftp=on ;iis_htmla=on ;iis_nntp=on ;iis_smtp=on 5. Create an ASRFiles folder and an ASRPNPFiles folder, and then copy Asr.sif and Asrpnp.sif to them. To do this, follow these steps: a. Create the ASRFiles folder and the ASRPNPFiles folder in the RemoteInstall folder on the RIS server. For example, create the following: ? E:\RemoteInstall ? ASRFiles ? ASRPNPFiles b. Copy the Asr.sif file from the ASR floppy disk to the ASRFiles folder. c. Copy the Asrpnp.sif file from the ASR floppy disk to the ASRPNPFiles folder. d. Determine the matching GUID by following one of these steps: ? Open Active Directory Users and Computers, and then locate the GUID for the domain account that was created. ? Start a PXE boot of the client computer, and then select a CD-based image install. After this install starts, locate the RemoteInstall\Tmp folder and notice that the Ristndrd.sif has been copied and renamed to the client computer's GUID.sif in the RemoteInstall\Tmp folder. ? Use the Microsoft Visual Basic scripting method to locate the GUID. For additional information about this method, click the following article number to view the article in the Microsoft Knowledge Base: 302467 How to prestage a RIS client computer using ADSI e. Rename the \\RISserver\Reminst\ASRFiles\Asr.sif file and the \\RISserver\Reminst\ASRPNPFiles\Asrpnp.sif file to the GUID that is assigned to the client computer. For example, if the GUID in the RemoteInstall\Tmp folder is 0000000000000000009879o689756, rename the Asr.sif file 0000000000000000009879o689756.sif. Note The Asr.sif file and the Asrpnp.sif file must match the GUID of the client computer that is being restored. If the GUID does not match, you receive an error message that states that the setup program cannot find the .sif files that are located in the ASRFiles folder or in the ASRPNPFiles folder. This error message references the GUID.sif file. 6. Edit the Asr.sif file that you renamed to include the GUID that is located in the ASRFiles folder. Add a command line to the Commands section to map the \\RISserver\Reminst\Setup\English\Images\ASRWINNETADSRC1 drive after the network is loaded. To do this, follow these steps. Note Do not perform this step if you are restoring from a tape backup. a. Create a batch file named Mapdrv.cmd that includes the following command: net use z: \\risnet1\reminstv\setup\english\images\asrwinnetadsrc1 Password1 /USER:risnet1\administrator b. Create an $oem$\C folder in the ASR ComputerName-OSVer \ folder. c. Copy the Mapdrv.cmd file to the ASR ComputerName-OSVer \$oem$\C folder. d. Edit your Ristndrd.sif file to set OEMPreinstall=Yes. e. Edit your Asr.sif file to call the Mapdrv.cmd as follows: [COMMANDS] 1=1,3000,0,"%SystemRoot%\system32\asr_fmt.exe","/restore" 2=1,4990,1,"%SystemRoot%\system32\asr_pfu.exe","/restore" 3=1,2000,1,"%SystemRoot%\system32\asr_ldm.exe","/restore" 4=1,3990,0,"%SystemRoot%\system32\cmd /c c:\mapdrv.cmd" 5=1,4000,1,"ntbackup","recover /1" Hope this helps. Mike Luo Microsoft Online Partner Support Get Secure! - http://www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Guest Rayees Posted August 23, 2007 Posted August 23, 2007 Re: How to automate ASR restore process Hi Mike I'm extremely happy to find the solution. However as I mentioned earlier I already use WDS (windows deployment services). So can I skip the RIS procedure ? or how do I go about doing the same with WDS. PLEASE HELP. Sorry to bother, I tried several options, but now I'm exhausted with all the option. With Kind Regards Rayees. "Mike Luo [MSFT]" <v-miluo@online.microsoft.com> wrote in message news:2pZZu5W5HHA.360@TK2MSFTNGHUB02.phx.gbl... > Hello, > > You may follow these steps: > > Setting up the RIS server to use ASR > 1. Set up the RIS server to support automation of the F12 PXE boot that > executes the ASR restore option. To do this, follow these steps: > a. Verify the BIOS boot order on the RIS server and on each of the client > computers. Position the hard disk first in the boot order, and then > position the PXE option second in the boot order. > b. Rename the current Startrom.com file as Startrom.bak (for backup > purposes). This file is located in the \\RISserver\Reminst\OSChooser\I386 > folder on the RIS server, > c. Rename the Startrom.n12 file as Startrom.com. This file is located in > the \\RISserver\Reminst\OSChooser\I386 folder on the RIS server. The new > version of Startrom.com automates the process when the user presses F12 to > prompt Trivial File Transfer Protocol (TFTP) for the initial download. > > 2. Make backups of the following files, and then rename them in the > \\RISserver\Reminst\OSChooser\Language folder: > ? Rename Welcome.osc as Welcome.bak. > ? Rename Login.osc as Login.bak. > ? Rename Install.osc as Install.bak. > ? Rename Warning.osc as Warning.bak. > > > Note As a best practice, make a backup copy of each .osc file before you > make any changes in the \\RISserver\Reminst\OSChooser\Language folder. > 3. Edit the following .osc files on the RIS server: a. Welcome.osc > <OSCML> > <META KEY=ENTER HREF="LOGIN"> > <META KEY=F3 ACTION="REBOOT"> > <META KEY=ESC HREF="LOGIN"> > <META KEY=F1 HREF="LOGIN"> > <TITLE> Client Installation Wizard > Welcome</TITLE> > <FOOTER> [ENTER] continue </FOOTER> > <META ACTION=AUTOENTER> > <BODY left=5 right=75> > > Welcome to the Client Installation Wizard. This Wizard helps you quickly > and easily set up a > new operating system on your computer. You can also use this Wizard to > keep your computer > up-to-date and to troubleshoot computer hardware problems. > > In the Wizard, you are prompted to use a valid user name, password, and > domain name to log on > to the network. If you do not have this information, contact your > network administrator > before continuing. > </BODY> > </OSCML> > Copy this code to the \\RISserver\Reminst\OSChooser folder, and then save > the file as Welcome.osc. After you add "META ACTION=AUTOENTER" to this > code, the user does not have to press ENTER in the Client Installation > Wizard because this action is automated. > b. Login.osc <OSCML> > <TITLE> Client Installation Wizard > Logon</TITLE> > <FOOTER> [ENTER] continue [ESC] clear [F1] help [F3] > restart computer</FOOTER> > <META KEY=F3 ACTION="REBOOT"> > <META KEY=F1 HREF="LOGINHLP"> > <META KEY=ESC HREF="LOGIN"> > <META ACTION="LOGIN"> > <META ACTION=AUTOENTER> > <BODY left=5 right=75> > > Type a valid user name, password, and domain name. You may use the > Internet-style logon > format (for example: someone@example.com). > > <FORM ACTION="CHOICE"> >   User name: <INPUT NAME="USERNAME" MAXLENGTH=255 TYPE=TEXT > VALUE=*****> >    Password: <INPUT NAME="*PASSWORD" TYPE=PASSWORD > MAXLENGTH=20 VALUE=*****> > Domain name: <INPUT NAME="USERDOMAIN" VALUE=%SERVERDOMAIN% > MAXLENGTH=255> > </FORM> > > Press the TAB key to move between the User name, Password, and Domain > name fields. > > You are connected to %SERVERNAME% > </BODY> > </OSCML> > Copy this code to the \\RISserver\Reminst\OSChooser\Language folder, and > then save the file as Login.osc. The two values that you must add to the > Login.osc file instead of ***** are the user name and the password for the > client. For example, if your user name is "ristest" and your password is > "deploy," these two lines will appear as follows:   User name: > <INPUT NAME="USERNAME" MAXLENGTH=255 TYPE=TEXT VALUE=ristest> >    Password: <INPUT NAME="*PASSWORD" TYPE=PASSWORD > MAXLENGTH=20 > VALUE=deploy><BR> > > Note If you do not prestage computers in your environment, the user name > that you create for RIS must have both of the following permissions: > ? Read > ? Create Computer Objects > > c. Install.osc <OSCML> > <META KEY=ESC ACTION="REBOOT"> > <META KEY=ENTER ACTION="REBOOT"> > <META ACTION=AUTOENTER> > <TITLE> Client Installation Wizard > Installation Information</TITLE> > <FOOTER> [ENTER] continue</FOOTER> > <BODY left=5 right=75> > > The following settings will be applied to this computer installation. > Verify these settings before continuing. > > Computer account: %MACHINENAME% > > Global Unique ID: %GUID% > > Server supporting this computer: %SERVERNAME% > > To begin Setup, press ENTER. If you are using the Remote Installation > Services boot floppy, remove the floppy > disk from the drive and press ENTER to continue. > </BODY> > </OSCML> > > Copy this code to the \\RISserver\Reminst\OSChooser\Language folder, and > then save the file as Install.osc. When you add "META ACTION=AUTOENTER" to > this code, the user does not have to press ENTER in the Client > Installation > Wizard because this action is automated. > d. Warning.osc <OSCML> > <META KEY=ENTER HREF="INSTALL"> > <META KEY=ESC HREF="CHOICE"> > <META KEY=F3 ACTION="REBOOT"> > <META SERVER ACTION="WARNING"> > <META ACTION=AUTOENTER> > <TITLE> Client Installation Wizard > Caution</TITLE> > <FOOTER> [ENTER] continue [ESC] cancel [F3] > restart computer</FOOTER> > <BODY left=5 right=75> > > <FLASH> > <PRE> > * * * C A U T I O N * * * > </PRE> > </FLASH> > > <BOLD> > <PRE> > All data on the hard drive will be deleted! > </PRE> > </BOLD> > > Before the new operating system is installed, this computer's hard drive > must be repartitioned > and formatted. All existing data on the drive will be deleted during > this process. > > To continue, press ENTER. To cancel the installation, press ESC. > </BODY> > </OSCML> > Copy this code to the \\RISserver\Reminst\OSChooser\Language folder, and > then save the file as Warning.osc. When you add "META ACTION=AUTOENTER" to > this code, the user does not have to press ENTER in the Client > Installation > Wizard because this action is automated. > > 4. Set the Group Policy to allow only automatic RIS setup installations. > To do this, follow these steps: > a. Click Start, point to All Programs, point to Administrative Tools, and > then click Active Directory Users and Computers. > b. Right-click your domain or the organizational unit where the policy > that you want to edit is applied, and then click Properties. > c. Click the Group Policy tab. > d. Click Default Domain Policy, and then click Edit. > e. In the left pane, expand User Configuration, and then expand Windows > Settings. > f. Click Remote Installation Services. > g. In the right pane, double-click Choice Options. > h. In the Choice Options Properties dialog box, select the following > options: > ? Under Automatic Setup, click Disabled . > ? Under Custom Setup, click Disabled . > ? Under Restart Setup, click Disabled . > ? Under Tools, click Enabled . > Then click OK. > i. Close the Group Policy Object Editor, and then click OK in the > Properties box for your domain. > > Creating an ASR backup set > To create an ASR backup that is set to a tape backup or to create an ASR > backup that is set to the \\RISserver\Reminst\Setup\English\Images\ > ASRImageName folder as Asr.bkf by using the Backup utility in Windows > Server 2003, follow these steps: > 1. Create a new Windows Server 2003 CD-based image on the RIS server, and > name the image folder the same as the corresponding computer name. > 2. On the computer that performs the ASR backup, map network drive Z to > the folder on the RIS server that contains the image that you created. > When > you restore the image with ASR later, it automatically locates the correct > files from the Asr.sif file and the Mapdrv.cmd file on network drive Z. > For > example, map the \\RISserver\Reminst\Setup\English\Images\ ASRImageName > folder to network drive Z on the computer where the ASR backup is > performed. > 3. Click Start, point to All Programs, point to Accessories, and then > click Backup. > 4. To create an ASR backup set in the Backup or Restore Wizard, do one of > the following > > Note By default, the Backup or Restore Wizard starts, unless it is > disabled. > a. To create an ASR backup set in the Backup or Restore Wizard, click to > select All information on this computer in the What do you want to backup? > area. > b. If the Backup or Restore Wizard is disabled, create an ASR set in > Advanced Mode. In the Backup Utility dialog box, click ASR Wizard on the > Tools menu, and then follow the instructions that appear on your screen. > > Installing the new build image on the RIS server > Note You must first create a CD-based image of the operating system that > you want to use for ASR. In all cases with RIS images, you must create a > CD-based image that provides backup files for subsequent RIPrep, ASR, or > WinPE images that you might create. Therefore, for every operating system > that you use for ASR, RIPrep, or WinPE images, you must have a CD-based > image that corresponds to the binary version of that operating system. For > example, you might need an image that corresponds to Windows Server 2003, > Windows Server 2003 Service Pack 1, and so on. To install the new build > image on the RIS server, follow these steps: > 1. Click Start, and then click Run. > 2. Type risetup.exe , click OK, and then follow the steps to complete the > wizard. > > Note If this is a clean install of the volume that contains the build > images, set the Tool.osc file so that the Tools image (Tools.osc) can be > selected automatically. This can be done in either of the following two > ways: a. If there is only one Tools image on the RIS server, remove the > "NOAUTO" text from the default Tools.osc file. > b. If there is more than one Tools image, leave the "NOAUTO" text > unchanged . The following OSCML section from the default Tools.osc file > shows where the "NOAUTO" text is located: <OSCML> > <META KEY=F3 ACTION="REBOOT"> > <META KEY=F1 HREF="TOOLSHLP"> > <META KEY=ESC HREF="CHOICE"> > <META SERVER ACTION="ENUM TOOLS CMDCONS"> > <TITLE> Client Installation Wizard > Tools</TITLE> > <FOOTER> [ENTER] continue [ESC] go back [F1] help [F3] > restart > computer</FOOTER> > <BODY left=5 right=75> > <BR> > <BR> > Use the arrow keys to select one of the following options: > <BR> > <P left=8> > <FORM ACTION="LAUNCH"> > <SELECT NAME="SIF" NOAUTO SIZE=12> > %OPTIONS% > </SELECT> > </FORM> > </P> > <BOLD>Description:</BOLD>   > <TIPAREA> > </BODY> > </OSCML> > > > If this is not a clean install of the volume that contains the build > images > or if the Tool.osc file has been modified, you must select the Select old > menu screens option during RIS setup to make sure that the Tool.osc file > is > not overwritten. > 3. Copy the build image to a new name in the current folder. The name of > the new image folder is not important, but it will be used to identify > where bits are copied in the future. For example, the first image is > located in E:\RemoteInstall\Setup\English\Images\Win.Net¨CADS, and the > copied image is located in E:\RemoteInstall\Setup\English\Images\ > ASRComputerName BK-ADS. > > Note When you copy the CD-based image, you do not want to modify the image > that is required for the backup files. Therefore, you must copy the > CD-based image into a new folder and use the following naming convention > to > rename the image: > > ASR ComputerName operating_system_version > > ASR indicates that this image is used for an ASR. ComputerName identifies > the exact computer that this ASR backup/disaster recovery image belongs > to. > (Because ASR images are computer-specific, the images can only be used for > the computer installation that they were originally created from). OSVer > specifies the operating system version for this image. > 4. Update the Ristndrd.sif file that is located in the > \\RISserver\Reminst\Setup\English\Images\ASR ComputerName-OSVer > \i386\Templates folder so that the copied image supports ASR, and then > rename the file Asr.sif. Do not confuse this Asr.sif file with the actual > Asr.sif file that the Windows Server 2003 Backup utility generates. > > Note Modify the Ristndrd.sif answer file in the newly created ASR > ComputerName-OSVer image folder, not in the CD-based image folder that you > originally created by using the Risetup.exe tool and copied from. > > The following sample Asr.sif file contains the specific changes that you > must make to the [OSChooser] section to support a Tools (ASR) image: > [data] > floppyless = "1" > msdosinitiated = "1" > OriSrc = "\\%SERVERNAME%\RemoteInstall\%INSTALLPATH%\%MACHINETYPE%" > OriTyp = "4" > LocalSourceOnCD = 1 > > [setupData] > OsLoadOptions = "/noguiboot /fastdetect" > SetupSourceDevice = > "\Device\LanmanRedirector\%SERVERNAME%\RemoteInstall\%INSTALLPATH%" > > [unattended] > OemPreinstall = no > FileSystem = LeaveAlone > ExtendOEMPartition = 0 > TargetPath = \WINDOWS > OemSkipEula = yes > InstallFilesPath = > "\\%SERVERNAME%\RemoteInstall\%INSTALLPATH%\%MACHINETYPE%" > LegacyNIC = 1 > > [userData] > FullName = "Microsoft Corporation" > OrgName = "Microsoft Corporation" > ComputerName = %MACHINENAME% > ProductID = "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" > > [GuiUnattended] > OemSkipWelcome = 1 > OemSkipRegional = 1 > AdminPassword = "Storage12" > AutoLogon = yes > AutoLogonCount = 1000 > TimeZone = 4 > > [LicenseFilePrintData] > AutoMode = PerSeat > > [GuiRunOnce] > > > [Display] > BitsPerPel = 16 > XResolution = 800 > YResolution = 600 > VRefresh = 60 > > [Networking] > [NetServices] > MS_Server=params.MS_PSched > > [identification] > JoinDomain = %MACHINEDOMAIN% > DoOldStyleDomainJoin = Yes > > [RemoteInstall] > Repartition = yes > UseWholeDisk = yes > > [OSChooser] > ASRFile=asrpnpfiles\%guid%.sif > ASRINFFile=\Device\LanmanRedirector\%SERVERNAME%\RemoteInstall\ASRFiles\%gui > d%.sif > Description ="ASRMachineName-2003-ADS(Backup-Date)" > Help ="This image Restores and ASR backup image of Operating System for > Dated date " > LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" > ImageType = "ASR" > Version="5.1 (0)" > > [Components] > ;ApplicationServer = OFF > ;iis_common = ON > ;iis_inetmgr = ON > ;iis_pwmgr = ON > ;iis_www = ON > ;iis_ftp=on > ;iis_htmla=on > ;iis_nntp=on > ;iis_smtp=on > > > 5. Create an ASRFiles folder and an ASRPNPFiles folder, and then copy > Asr.sif and Asrpnp.sif to them. To do this, follow these steps: > a. Create the ASRFiles folder and the ASRPNPFiles folder in the > RemoteInstall folder on the RIS server. For example, create the following: > ? E:\RemoteInstall ? ASRFiles > ? ASRPNPFiles > > > b. Copy the Asr.sif file from the ASR floppy disk to the ASRFiles folder. > c. Copy the Asrpnp.sif file from the ASR floppy disk to the ASRPNPFiles > folder. > d. Determine the matching GUID by following one of these steps: > ? Open Active Directory Users and Computers, and then locate the GUID for > the domain account that was created. > ? Start a PXE boot of the client computer, and then select a CD-based > image > install. After this install starts, locate the RemoteInstall\Tmp folder > and > notice that the Ristndrd.sif has been copied and renamed to the client > computer's GUID.sif in the RemoteInstall\Tmp folder. > ? Use the Microsoft Visual Basic scripting method to locate the GUID. For > additional information about this method, click the following article > number to view the article in the Microsoft Knowledge Base: > 302467 How to prestage a RIS client computer using ADSI > > e. Rename the \\RISserver\Reminst\ASRFiles\Asr.sif file and the > \\RISserver\Reminst\ASRPNPFiles\Asrpnp.sif file to the GUID that is > assigned to the client computer. For example, if the GUID in the > RemoteInstall\Tmp folder is 0000000000000000009879o689756, rename the > Asr.sif file 0000000000000000009879o689756.sif. > > Note The Asr.sif file and the Asrpnp.sif file must match the GUID of the > client computer that is being restored. If the GUID does not match, you > receive an error message that states that the setup program cannot find > the > sif files that are located in the ASRFiles folder or in the ASRPNPFiles > folder. This error message references the GUID.sif file. > > 6. Edit the Asr.sif file that you renamed to include the GUID that is > located in the ASRFiles folder. Add a command line to the Commands section > to map the \\RISserver\Reminst\Setup\English\Images\ASRWINNETADSRC1 drive > after the network is loaded. To do this, follow these steps. > > Note Do not perform this step if you are restoring from a tape backup. > a. Create a batch file named Mapdrv.cmd that includes the following > command: net use z: > \\risnet1\reminstv\setup\english\images\asrwinnetadsrc1 Password1 > /USER:risnet1\administrator > > b. Create an $oem$\C folder in the ASR ComputerName-OSVer \ folder. > c. Copy the Mapdrv.cmd file to the ASR ComputerName-OSVer \$oem$\C > folder. > > d. Edit your Ristndrd.sif file to set OEMPreinstall=Yes. > e. Edit your Asr.sif file to call the Mapdrv.cmd as follows: [COMMANDS] > 1=1,3000,0,"%SystemRoot%\system32\asr_fmt.exe","/restore" > 2=1,4990,1,"%SystemRoot%\system32\asr_pfu.exe","/restore" > 3=1,2000,1,"%SystemRoot%\system32\asr_ldm.exe","/restore" > 4=1,3990,0,"%SystemRoot%\system32\cmd /c c:\mapdrv.cmd" > 5=1,4000,1,"ntbackup","recover /1" > > Hope this helps. > > Mike Luo > > Microsoft Online Partner Support > Get Secure! - http://www.microsoft.com/security > > ===================================================== > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. > >
Guest Mike Luo [MSFT] Posted August 24, 2007 Posted August 24, 2007 Re: How to automate ASR restore process Hello, I only find out the solution for RIS, not for WDS. I don't ensure the ASR work fine on WDS. I suggest you install a RIS to support the ASR. As you know, WDS is the upgrade of RIS, that is compatile with RIS and ASR might run on WDS. You also may try to refer to the configuration for RIS to configure WDS. Thanks & Regards, Mike Luo Microsoft Online Partner Support Get Secure! - http://www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Guest Rayees Posted August 25, 2007 Posted August 25, 2007 Re: How to automate ASR restore process Mike Thanks a lot for all the help, I will try out the same. The information which you provided was quiet helpful, Thanks once again Regards Rayees "Mike Luo [MSFT]" <v-miluo@online.microsoft.com> wrote in message news:gXGPosj5HHA.4200@TK2MSFTNGHUB02.phx.gbl... > Hello, > > I only find out the solution for RIS, not for WDS. I don't ensure the ASR > work fine on WDS. I suggest you install a RIS to support the ASR. As you > know, WDS is the upgrade of RIS, that is compatile with RIS and ASR might > run on WDS. You also may try to refer to the configuration for RIS to > configure WDS. > > Thanks & Regards, > > Mike Luo > > Microsoft Online Partner Support > Get Secure! - http://www.microsoft.com/security > > ===================================================== > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. >
Guest Mike Luo [MSFT] Posted August 27, 2007 Posted August 27, 2007 Re: How to automate ASR restore process Appreciate your response. I am very glad to hear that information be helpful to you. It is my pleasure to be of assistance. Have a nice day! Mike Luo Microsoft Online Partner Support Get Secure! - http://www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Guest Joe Reynolds Posted October 2, 2007 Posted October 2, 2007 Restore IIS Different Machine Restore IIS Different Machine I have 2 Windows 2003 servers. One named PRIMARY the other SECONDARY. Primary is the live server used for serving web sites. BOTH are set up as a standalone server. Both are online and managed remotely. SECONDARY is there as a backup server. My question is related to what information I need to quickly make SECONDARY the live server -- forgetting content. For example, I believe I can backup the IIS metabase from PRIMARY, store on SECONDARY, and restore to SECONDARY. Is there any information available that details what backup files, etc. are needed to have SECONDARY do the same things as PRIMARY in regard to serving web sites, ftp, media server, etc? Is a restore of the metabase all that is needed?
Guest Anthony Posted October 3, 2007 Posted October 3, 2007 Re: Restore IIS Different Machine Re: Restore IIS Different Machine Joe, Here's some information: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/5e7e923c-b374-4872-a8f5-da85ec1315fd.mspx?mfr=true You can use iisback.vbs to make a copy of the primary IIS. You will need to get another certificate if you are using SSL. You may as well have them both running with Load Balancing, Hope that helps, Anthony, http://www.airdesk.co.uk "Joe Reynolds" <JoeReynolds@discussions.microsoft.com> wrote in message news:D8275083-11A9-411A-917B-E5148DBB8D1F@microsoft.com... >I have 2 Windows 2003 servers. One named PRIMARY the other SECONDARY. > Primary is the live server used for serving web sites. BOTH are set up as > a > standalone server. Both are online and managed remotely. > > SECONDARY is there as a backup server. My question is related to what > information I need to quickly make SECONDARY the live server -- forgetting > content. For example, I believe I can backup the IIS metabase from > PRIMARY, > store on SECONDARY, and restore to SECONDARY. > > Is there any information available that details what backup files, etc. > are > needed to have SECONDARY do the same things as PRIMARY in regard to > serving > web sites, ftp, media server, etc? Is a restore of the metabase all that > is > needed?
Guest Joe Reynolds Posted October 3, 2007 Posted October 3, 2007 Re: Restore IIS Different Machine Re: Restore IIS Different Machine Anthony, thanks for your response. My reading of the restore to another machine info indicates I should edit and delete all references to ACLs and passwords from the metabase restore file prior to restoring to another machine. Is this correct? "Anthony" wrote: > Joe, > Here's some information: > http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/5e7e923c-b374-4872-a8f5-da85ec1315fd.mspx?mfr=true > You can use iisback.vbs to make a copy of the primary IIS. You will need to > get another certificate if you are using SSL. You may as well have them both > running with Load Balancing, > Hope that helps, > Anthony, http://www.airdesk.co.uk > > > > "Joe Reynolds" <JoeReynolds@discussions.microsoft.com> wrote in message > news:D8275083-11A9-411A-917B-E5148DBB8D1F@microsoft.com... > >I have 2 Windows 2003 servers. One named PRIMARY the other SECONDARY. > > Primary is the live server used for serving web sites. BOTH are set up as > > a > > standalone server. Both are online and managed remotely. > > > > SECONDARY is there as a backup server. My question is related to what > > information I need to quickly make SECONDARY the live server -- forgetting > > content. For example, I believe I can backup the IIS metabase from > > PRIMARY, > > store on SECONDARY, and restore to SECONDARY. > > > > Is there any information available that details what backup files, etc. > > are > > needed to have SECONDARY do the same things as PRIMARY in regard to > > serving > > web sites, ftp, media server, etc? Is a restore of the metabase all that > > is > > needed? > > >
Guest Joe Reynolds Posted October 3, 2007 Posted October 3, 2007 Re: Restore IIS Different Machine Re: Restore IIS Different Machine In regard to the SSL certificates, I suppose I could rename SECONDARY to PRIMARY (assuming PRIMARY is offline) and then restore the certificates from PRIMARY? "Anthony" wrote: > Joe, > Here's some information: > http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/5e7e923c-b374-4872-a8f5-da85ec1315fd.mspx?mfr=true > You can use iisback.vbs to make a copy of the primary IIS. You will need to > get another certificate if you are using SSL. You may as well have them both > running with Load Balancing, > Hope that helps, > Anthony, http://www.airdesk.co.uk > > > > "Joe Reynolds" <JoeReynolds@discussions.microsoft.com> wrote in message > news:D8275083-11A9-411A-917B-E5148DBB8D1F@microsoft.com... > >I have 2 Windows 2003 servers. One named PRIMARY the other SECONDARY. > > Primary is the live server used for serving web sites. BOTH are set up as > > a > > standalone server. Both are online and managed remotely. > > > > SECONDARY is there as a backup server. My question is related to what > > information I need to quickly make SECONDARY the live server -- forgetting > > content. For example, I believe I can backup the IIS metabase from > > PRIMARY, > > store on SECONDARY, and restore to SECONDARY. > > > > Is there any information available that details what backup files, etc. > > are > > needed to have SECONDARY do the same things as PRIMARY in regard to > > serving > > web sites, ftp, media server, etc? Is a restore of the metabase all that > > is > > needed? > > >
Guest Anthony Posted October 3, 2007 Posted October 3, 2007 Re: Restore IIS Different Machine Re: Restore IIS Different Machine Hi Joe, If you read the configuration xml you can get a pretty good idea of what you can move and what you need to amend. You need to remove or amend anything that is machine-specific. My approach is to set up the IIS on Secondary as you want it to be, and then only import the parts you want, but obviously you can get much more complex than that. For the SSL certificate, you could either export it, or you could set the server up with an additional certificate with the same name. If you have two servers up and running, my view is that you may as well use them rather than have one on standby. Hope that helps, Anthony, http://www.airdesk.co.uk "Joe Reynolds" <JoeReynolds@discussions.microsoft.com> wrote in message news:888EA25B-9816-415F-95FC-3CB2CCDF86D6@microsoft.com... > Anthony, thanks for your response. My reading of the restore to another > machine info indicates I should edit and delete all references to ACLs and > passwords from the metabase restore file prior to restoring to another > machine. Is this correct? > > "Anthony" wrote: > >> Joe, >> Here's some information: >> http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/5e7e923c-b374-4872-a8f5-da85ec1315fd.mspx?mfr=true >> You can use iisback.vbs to make a copy of the primary IIS. You will need >> to >> get another certificate if you are using SSL. You may as well have them >> both >> running with Load Balancing, >> Hope that helps, >> Anthony, http://www.airdesk.co.uk >> >> >> >> "Joe Reynolds" <JoeReynolds@discussions.microsoft.com> wrote in message >> news:D8275083-11A9-411A-917B-E5148DBB8D1F@microsoft.com... >> >I have 2 Windows 2003 servers. One named PRIMARY the other SECONDARY. >> > Primary is the live server used for serving web sites. BOTH are set up >> > as >> > a >> > standalone server. Both are online and managed remotely. >> > >> > SECONDARY is there as a backup server. My question is related to what >> > information I need to quickly make SECONDARY the live server -- >> > forgetting >> > content. For example, I believe I can backup the IIS metabase from >> > PRIMARY, >> > store on SECONDARY, and restore to SECONDARY. >> > >> > Is there any information available that details what backup files, etc. >> > are >> > needed to have SECONDARY do the same things as PRIMARY in regard to >> > serving >> > web sites, ftp, media server, etc? Is a restore of the metabase all >> > that >> > is >> > needed? >> >> >>
Guest Joe Reynolds Posted October 3, 2007 Posted October 3, 2007 Re: Restore IIS Different Machine Re: Restore IIS Different Machine The standby server is essentially configured to become the live server if the primary server should go down. While it is standby, it does serve live as a Windows Media Server. If the primary server goes down I need to restore the latest sql databases to the secondary sever, and restore the IIS metabase from the primary to the secondary so all the web sites, etc have proper IPs. I'm not certain what else I need to do. Just seems like there should be some "templated" scenarios out there for what I want to do, short of trial and error. "Anthony" wrote: > Hi Joe, > If you read the configuration xml you can get a pretty good idea of what you > can move and what you need to amend. You need to remove or amend anything > that is machine-specific. My approach is to set up the IIS on Secondary as > you want it to be, and then only import the parts you want, but obviously > you can get much more complex than that. > For the SSL certificate, you could either export it, or you could set the > server up with an additional certificate with the same name. If you have two > servers up and running, my view is that you may as well use them rather than > have one on standby. > Hope that helps, > Anthony, http://www.airdesk.co.uk > > > > > "Joe Reynolds" <JoeReynolds@discussions.microsoft.com> wrote in message > news:888EA25B-9816-415F-95FC-3CB2CCDF86D6@microsoft.com... > > Anthony, thanks for your response. My reading of the restore to another > > machine info indicates I should edit and delete all references to ACLs and > > passwords from the metabase restore file prior to restoring to another > > machine. Is this correct? > > > > "Anthony" wrote: > > > >> Joe, > >> Here's some information: > >> http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/5e7e923c-b374-4872-a8f5-da85ec1315fd.mspx?mfr=true > >> You can use iisback.vbs to make a copy of the primary IIS. You will need > >> to > >> get another certificate if you are using SSL. You may as well have them > >> both > >> running with Load Balancing, > >> Hope that helps, > >> Anthony, http://www.airdesk.co.uk > >> > >> > >> > >> "Joe Reynolds" <JoeReynolds@discussions.microsoft.com> wrote in message > >> news:D8275083-11A9-411A-917B-E5148DBB8D1F@microsoft.com... > >> >I have 2 Windows 2003 servers. One named PRIMARY the other SECONDARY. > >> > Primary is the live server used for serving web sites. BOTH are set up > >> > as > >> > a > >> > standalone server. Both are online and managed remotely. > >> > > >> > SECONDARY is there as a backup server. My question is related to what > >> > information I need to quickly make SECONDARY the live server -- > >> > forgetting > >> > content. For example, I believe I can backup the IIS metabase from > >> > PRIMARY, > >> > store on SECONDARY, and restore to SECONDARY. > >> > > >> > Is there any information available that details what backup files, etc. > >> > are > >> > needed to have SECONDARY do the same things as PRIMARY in regard to > >> > serving > >> > web sites, ftp, media server, etc? Is a restore of the metabase all > >> > that > >> > is > >> > needed? > >> > >> > >> > > >
Recommended Posts