• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 877
  • Last Modified:

windows xp Sysprep

need help this is very urgent. Every time i use Sysprep using windows xp w/sp 2 the IIS breaks. how would I solve this problem.
  • 4
  • 4
1 Solution
Describe what you mean by "IIS breaks"

Something you should understand about IIS is that many of the items in the IIS metabase are machine and system specific.  They don't take well to imaging.

What you should do is backup your IIS metabase from within the Information Systems Manager snap-in.

Save this metabase on the system you're imaging.

Then when you image a system, you'll need to restore the the metabase WITHOUT the machine specific variables.  To accomodate this microsoft has included two VBS files called iisback.vbs and iiscnfg.vbs (might be iisconfig.vbs, I can't remember the exact file name)

Read this document for detailed instructions on how to backup and restore an IIS metabase.

Oh, and also remember that the IIS user accounts need to be renamed.  THey are specific to the name of the server.


it is also important to note that part this sequence can be automated in your sysprep file.  One of the options in the setupmgr.exe tool is commands to run at the end of the installation.  You can run command line actions at the end of your sysprep sequence that will restore your IIS metabase.  Now that the computer has a unique name it will work just fine.

It's also possible to rename the user accounts from the command line.

There is a free tool called renuser that you could put in your image.

I think the command "renuser IUSR_SERVERNAME IUSER_%computername% SERVERNAME" will work, though I've never tried it.

You would then repeat using IWAM_SERVERNAME
jolivareAuthor Commented:
what i mean about IIS("Internet Information Services") breaks is the the subfolders disapear after it runs the sysprep setup. if  I only image the system then i works fine it will not break but if i image the system and do a sysprep ("System Preparation Tool and Answer File Usage") then it will break.
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Well that's a bit strange.  So far as I understand, sysprep should only be delete any files contained within the sysprep folder.  It cleans itself up as part of the installation.  If for some reason the folders you're missing are contained in the sysprep folder then that would be the reason.

I can't think of any other reason sysprep would randomly delete IIS directories.

Is this the inetpub directory?
jolivareAuthor Commented:
I sorry I don't know what you mean about inetpub direcitory? you mean the subfolder under the IIS component?

do you know any script that will install a windows component in this case IIS?
jolivareAuthor Commented:
Here is the solution to this problem. I found it on microsoft.com. all you need is to delete a file before you do the sysprep. Here is what you need to do:

To work around this problem, use one of the following methods:• Install the Windows XP SP2 Sysprep image from a Windows XP SP2 integrated source.
• Install Windows XP SP2 before you install IIS.  
• Delete the Iischema-update.md0 file before you run Sysprep. To do this, follow these steps:1. Open Windows Explorer.
2. Locate and then double-click the %SystemRoot%\System32\Inetsrv\MetaBack folder.
3. Right-click iischema-update.md0, and then click Delete.
4. When you are prompted to confirm the deletion, click Yes.
5. Quit Windows Explorer.

here is the site for more info: http://support.microsoft.com/?kbid=889073
jolivareAuthor Commented:
I'm going to give the points to someone to close this question. Thank you all for all your answer. I found the correct answer on the microsoft web site. I'll give the points to mslunecka because mslunecka answer first and try to help me.
By inetpub I meant the C:\inetpub  directory.  This is the default location in which IIS stores your WWW documents.  Your default website is usually housed at c:\inetpub\wwwroot

Your solution is actually what I was refering to...though I didn't know Microsoft had an article specifically about it.  The metabase contains machine-specific language that will be different on every computer, even if you reload the same computer twice it will need a new metabase.

You do need to be careful with the IUSR and IWAM accounts, though, because if you don't change the names of those accounts on each server after you image them, you could run into the problem with cross-site security problems.  The same username is being granted access on multiple servers when maybe they shouldn't be.  

Good luck!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now