Tripredacus

Welcome to the MSFN!

Welcome to the MSFN!

All day NHL Trade Deadline talk!

Speccy should be able to tell you the name of the board.

I posted an example XML that will boot a system into Audit mode, here. This example has the Win7 install key, so you need to change it to your Vista install key. Please make a new topic if you have further questions, as this isn't specifically related to the Guide.

I don't know if you are allowed to brand the logon screen. You can do the Windows Welcome. But you already have this documentation! It is in the OPK User's Guide under Windows 7 OEM Customization Opportunities, First Experience.

SBS will create an Active Directory domain in your house! Do you have a need for this? You may be wanting to use something like Sharepoint Server, but honestly, even that may be too much. Also before you attempt to put a server in your home (if you are in the US) make sure you do not have a residential account for your ISP. Reason being, most ISP has running a server on residential service account is against TOC. You can lose your service, but if you do not know which to do, call them and ask what options you can have.

For the username, you type in COMPUTERA'SNAME\username That will change the "current" domain away from your computer B.

I'm not sure how to use an unattend on the boot image (from a partition), you could try rebuilding the boot wim but there is a problem. The Vista WinRE really isn't anything besides a WinPE and the recovery front-end. That was the problem with Vista, MS made you write the recovery software. Anyways, about the Fujitsu files, there is no reason those actually need to be there to run a recovery.

I was wondering if that SID in the indexing logs matches the SID on your user account, which can be found in the Registry under HKEY_USERS. I can definately see a problem in trying to index a foreign disk. I have foreign disks (hard drives from other OS/computers) in two of my Win7 machines (work and home) and haven't gotten an error like this. However, I am not certain if I have the index turned on for those drives, and I would imagine that they are not set to be indexed. However, at home I did have problems with one of my foreign disks (from an XP PC) and I had to take ownership of the entire volume. So unless someone else can come up with another idea, I can see two options: 1. set permissions to allow the SYSTEM "account" read/write access to the entire volume. 2. take ownership (to your user account) of the entire volume. The problem with either of these is that the process can take a long time, as it depends on the amount of files involved.

When you tried the second (bad) video card in the PC by itself, do you put it in the slot the other (good) video card was in?

You should use an autounattend.xml to boot your OS into Audit Mode. If you use the Ctrl+Shift+F3 after install, you end up losing a generalize.

First take the XML I posted and change the language settings. Use that to do your install and see if it prompts you for anything. You can remove the drive formatting sections if you want. You do not need to remove the product key I have in there either. That product key is an install key.

I find it disheartening that Fujitsu would leave these files in their image... whatever happens, these files are non-redistributable, so you cannot share them or even post their code. Just an FYI.

OK, this item here is a SID: {S-1-5-21-2201963446-2159910242-3709398457-500} It is a unique identifier that is attached to accounts and to permissions. The drive in question, is it read or written to from both OSes at some point? Also, this 1TB, was it first formatted by the XP or Win7 OS, or did it come from use in another computer? Let's see if this SID is from your Win7 system or from something else. You can see your SID in the registry in HKEY_USERS. There will be (at least) 6 items. For example mine has: .DEFAULT S-1-5-18 S-1-5-19 S-1-5-20 FULL SID FULL SID_Classes I'm not going to post my full SID, not the point. The two long lines (the number and the one with _Classes) will match and this is your SID. This number may or may not be different from the one that appeared in your event log. The reason I ask about the OS is because a lot of people here post about things other than what is in their profile information. And the point I'm getting to here (I haven't looked up this warning yet) is perhaps an ownership or permissions issue that is causing the index to fail.

Figured I'd throw this out here in case anyone has any ideas. I am currently out a test server and won't have one until later this week. In the meantime, I've been experimenting with VMs. Here is my set up: VM1 is running Server 2008 RTM Standard. It is Domain Controller, DHCP, DNS, WDS. I have added in the BOOT.WIM (Win7 x86 SP1) to Boot Images, and the matching INSTALL.WIM to Install Images. I then create XML files to handle authentication on the Boot Image(s), and XML attached to Pro and Home Premium Install Images to get them to boot into Audit Mode and the default install key. I have created a Capture Image from within WDS. I create a user account. I assign this account Full Control Permissions on Reminst\Images\ImageGroup. VM2 is blank, does a PXE boot to WDS. Select WIn7 Setup option. Select Win7 Pro. It installs reboots and boots to Audit Mode, so all XML works. I then sysprep /generalize /reboot /audit and boot to the Capture Image. I select the volume with the OS on it, connect to the WDS Server and enter in the credentials that has write access to the image group. The error I receive is: First thing to note is the Capture Boot Image prompts for credentials, so evidently the Server specified XML (that is used properly on the Setup WIM) is ignored. I use the same account that is also used for deployment. This account does have admin rights. Second, the WIM is created, as I can find it on the drive. It appears that only the upload portion is the problem. Third, since I am using a VM, I have chosen to save the image on the VM's hard drive, which is also the drive the capture is done from. Could this be a problem? I am not sure if it is worth the time to have it capture to either the Server Guest or the Host OS... Any thoughts?

Well since you are specifying audit mode, it may be easier for you to use 1 XML for install to Audit, and a second XML to use with sysprep. You still have some things mixed up between specialize and oobeSystem, such as OEM information. And you are also specifying things in multiple locations, such as registered organization. You may also want to check with your Partner rep to see if you are allowed to specify registered owner and organization, since it is not in the list of allowed customizations. A reason why you shouldn't use a single unattend is because you are specifying Audit mode in oobeSystem. A possible result from sysprep is that the machine would always go into audit mode, even if you specify OOBE from the cmdline. So instead of jumping all in with a super-duper XML, try to get the install to audit mode experience done, then add stuff later to be handled during sysprep.

There are always more updates. And there will be more updates after you get IE8 in there! Did you search the forum already? I'm sure there is a topic about it.

Let's start with autounattend-cleaned.xml... Line 3, what is up with this: <servicing></servicing> SetupUILanguage not specified... Your Code: <InputLocale>2057:00000809</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-GB</UILanguage> <UILanguageFallback>en-GB</UILanguageFallback> <UserLocale>2057:00000809</UserLocale> Mine: <SetupUILanguage> <UILanguage>en-us</UILanguage> </SetupUILanguage> <InputLocale>0409:00000409</InputLocale> <SystemLocale>en-us</SystemLocale> <UILanguage>en-us</UILanguage> <UserLocale>en-US</UserLocale> Your Languages (from above) are in the Microsoft-Windows-International-Core component in the oobeSystem Pass. This should be Microsoft-Windows-International-Core-WinPE and in the WindowsPE pass. You have Microsoft-Windows-Shell-Setup in two different passes. If you want your install to boot into Audit Mode, you do not need this in your AUTOUNATTEND.XML. These objects go into the XML you use with Sysprep (SYSPREP.XML) . Actually you have so much wrong in this file even I'm getting confused looking at it. Just take a look at my example, which is for Win7 Pro x64 and puts a machine in Audit Mode: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserData> <ProductKey> <Key>HYF8J-CVRMY-CM74G-RPHKF-PW487</Key> <WillShowUI>OnError</WillShowUI> </ProductKey> <AcceptEula>true</AcceptEula> </UserData> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> <DiskConfiguration> <Disk wcm:action="add"> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>true</Extend> <Format>NTFS</Format> <Label>System</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>20480</Size> <Extend>false</Extend> <Type>Primary</Type> </CreatePartition> </CreatePartitions> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration> </component> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-us</UILanguage> </SetupUILanguage> <InputLocale>0409:00000409</InputLocale> <SystemLocale>en-us</SystemLocale> <UILanguage>en-us</UILanguage> <UserLocale>en-US</UserLocale> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Reseal> <Mode>Audit</Mode> </Reseal> </component> </settings> <cpi:offlineImage cpi:source="catalog:d:/sources/install_windows vista business.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> Your OOBE.XML is fine, which you just put it in its place and Sysprep finds it. After you boot into Audit Mode, you can use sysprep and /unattend: switch to specific the XML you want to add your OS Settings. Example: c:\windows\system32\sysprep\sysprep.exe /oobe /shutdown /generalize /unattend:c:\windows\panther\sysprep.xml.

No need to ask!

I am aware of that user's page. Also, ViewPoint doesn't seem to be the company those assets were sold to. Unless you can find where exactly those assets (Transitions) are held by, you cannot be certain that the product is indeed abandonware and in the public.

When you use Ctrl+Shift+F3 to enter audit mode. After you boot to the desktop, close the sysprep box. Then from start -> run you type: c:\windows\system32\sysprep\sysprep.exe /oobe /reboot /unattend:path_to_unattend.xml. You probably should make sure your XML is validated, or else you may have to reinstall again if Setup/Sysprep doesn't like the file, or if it isn't built properly.

Let's start with some info from you. 1. What OS version? 2. RTM or SP1? 3. x86 or x64? 4. Any warnings or errors in Event Viewer? 5. What size volume is this occuring on? 6. Using RAID or JBOD? 7. What file system is on this volume?

Yeah come to think of it, this forum is pretty old.