Tripredacus

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.

I wonder if the excessively long topic title may be related.

Yes, wrapper worms are very old. Lucky you got past it. I first encountered one when I worked in college. It was possible to remove the virus but then nothing worked anymore!

Not going for the original joke I saw that Vista is malware... It is definately possible that some accounts have malware that is only started when their account logs in. So it would be safer to scan on each logon. For example, it is possible to modify the properties of a malware so that it cannot start or run properly. In this case, a malware scanner may not be able to find it, even though it is still present. I'm not sure how concerned you would be about having remnants sitting around.

It was explained to me that the Amps are drawn from the notebook (or device) so a power adapter that has a max potential of more amps than needed isn't necessarily a bad thing. That is, the adapter does not force those amps upon the device it is attached to. Of course the voltage is another story. Personally, I will discontinue use of this adapter once I get the correct one for it.

There seems to be an x64 putty available (among other things) here: http://www.chiark.greenend.org.uk/~sgtatham/putty/links.html

Its being worked on currently. Hope to see it back shortly.

I remember I used to use the practice of First Step: remove anything not needed. Of course, over the years I've forgotten to do that as often. It would have worked out well in your case I would imagine!

I am not able to locate who is the current owner of the Transitions product. This product first appeared as a demo/shareware in DirectX and IE 5.5. Just because we cannot find who owns that particular product now, doesn't mean that it is actually abandoneware or in the public domain. To err on the side of caution, we can only take the stance that brand removal on a product is illegal. Please read our forum rules. We don't have them to be mean.

Yes you should. Use Imagex /info to view the images contained in install.wim. Then use imagex /export to export the specific image you want. Next create a new DVD, and instead of the normal install.wim, use the one you exported. It must be called install.wim however!

The only way I have found is to install the drivers onto a system. Then use one of those Driver backup programs to get the driver off of there. I did this with some nForce notebook once and it worked.

Agree. I can confirm that Putty works in WinPE, or at least the telnet ability. I got to a logon prompt on my Server VM at least. I tested only x86 WinPE, do not have the ability to work with x64 at the moment. PS: Putty has always been portable.

Here's a good example of a mis-matched adapter in every day use. My MSI Wind U100 wants 20V and 2A I use a MSI MS-163K AC Adapter that gives 19V and 3.42A I don't normally have this, but a co-worker stole my regular AC Adapter...

All the people I know that work with such activities (converting records or tapes to MP3) do it manually. If there was some magic program that could do it for you (oh and hope your tape deck isn't set for continuous auto-reverse) it would probably not be free.

Is it normal to be putting in such large reg files. Have you tried splitting this up at all? Also, your example has an extra code tag at the top. I hope your reg file doesn't have that in there.