Tripredacus

I am getting a Code 43 (driver conflict) on the onboard video controller in the Device Manager on Vista Business RTM and SP1. The image was created on the same computer. Here is the history: - Start with a PC with a GeForce video card in it. - install Vista Business RTM (or SP1) and set up GPOs - do not install any software or drivers - sysprep and generalize and capture Now I want to make a different image that will be more hardware specific. I use the same computer but I take out the video card. After I drop the image, there is a Code 43 in the Device Manager. There is no other software installed. If I do a hand-load of Vista again, there is no flag. If I put XP on there, there is no flag. There is something in Vista that makes it think there is a problem with the video because it is on the PCI bus instead of the PCI-E bus? There is no trace of the video card's hardware ID in the registry, and no matter what drivers I use this does not go away. Onboard video is Intel Graphics. I have the last 3 driver versions to use. Any ideas?

Do your normal setup as the admin, and one of your programs that you call at the end can change the registry settings and then force a reboot. You may need to preauth the computer into your AD tho.

I don't think it matters if it is a card or onboard. But you might try the software option if your board allows you to do it.

WDS isn't designed to deploy XP images in that way. I redeploy XP via WinPE and not the WDS boot loader.

I remember MAKING MP3s... It would take 30 seconds to record the WAV Audio, 40 minutes to compress to a layer 3 wave and 20 minutes to convert to MP3. And that was just for a 30 second audio clip on a 133MHz PC... I was so happy when making MP3s became so much easier! ps: I use LimeWire and have the BT client (not full app) installed.

http://www.practicallynetworked.com/sharin...filesharing.htm http://www.practicallynetworked.com/sharin...aring/index.htm

You can use diskpart to reveal the hidden partition, that is, as long as it can see it. You would need to post a full info about the volume/disk/partition before I could tell you what commands to use.

That software boots into a Linux shell. You are right, you can't run the setup.exe from there. And you can't run it from the DOS prompt. Did you follow the rest of the instructions to make the Windows installation source? It seems pretty staight forward, you should get a menu and pick what you want to install.

You need to specify a few other registry keys. DefaultUserName DefaultPassword DefaultDomainName http://www.mydigitallife.info/2008/06/15/h...-domain-member/

I was the one who reported this issue as well. I have not resolved it and am instead going to (attempt) migrate our XP install to PXE via WinPE 2.0 instead. If it helps, this is my operating environment Server 2003 Standard x32 Windows OPK Tools (Vista SP1 release) WDS BDD2007 original thread: http://www.msfn.org/board/index.php?showtopic=123611

Welcome to the work of non-certified hardware. Unless you can get a 32bit 2008 driver in there, you might just be SOL. I'm encountering a similar problem with a 3ware 9550. Its a hope for the best situation to be honest. Typically, the Vista 32bit drivers should be good enough. You might have to edit the INF so you don't have to force the driver to be installed tho.

Also, blue "files" meaning their names are blue means they are compressed.

They may be marked hidden and you have it set to view hidden files. If so you just need to unhide it, which can be done in the properties window.

More information is required. Which model motherboard do you have? No Gigabyte motherboards listed on their site with the Intel 801 chipset support a socket 370 and 1024MB RAM. http://www.gigabyte.com.tw/Products/Mother...Type=socket+370 Any current gaming computers should require the following as minimum requirements: CPU: 2GHz RAM: 2GB Video: 128MB DirectX 9 compatible

GhostServer: Drive 2 fell off the array. We are thinking there is a bad slot. The RAID will get rebuilt on Monday and we can hopefully use it. New direction: This server will act as a backup server for VISTASERVER, since it seems to be having storage issues ATM. IMAGEX.WDS: Still trying to fix some of the previous errors. WDS is flaking out about not having a WinPE for x64 even though we use it every day. Disabled LDAP signing requirement, but its still complaining about not having a certificate... Disabled Windows Firewall, but the Filtering Service is still blocking ports. Code Integrity is saying that tcpip.sys doesn't match the hash. Power Management is saying that it couldn't apply powr settings to any of the 8 cores, and we should do a firmware update. Maybe we can do that today. Intel posted a new one for the S5000PSL just yesterday. Online Help says it can't update to the internet. No wonder there. DHCP service says it can't update DNS records... Not sure if we want it to update DNS records. There are only a handful of computers that should have a DNS record, all the rest are only on the network for maybe 2-3 days tops. It would be pointless for those to get recorded.

Source: Microsoft Windows Security Auditing Event ID: 5159 I am getting hundreds of these. The Windows Firewall is turned off. Even though, the Windows Firewall service was active. I disabled the service but these still appear. I attempted to use Process Monitor to view Process 4, but it could not read any of the Threads. Is there a newer version of Process Monitor that works properly in 64bit?

Another Event I am trying to get rid of. Source: BINLSVC Event ID: 1306 The default boot image Boot\x64\images\winpe.wim was not found for the x64 architecture On the boot tab of the WDS properties, both x86 and x64 boot images are listed. I am successfully able to boot x86 and x64 architectures. The following command gives an error: bcdedit.exe /enum /all /store:d:\remoteinstall\boot\x64\default.bcd invalid switch /all ???

I have disabled LDAP signing requirements, however I still get this message. Computer Configuration\Policies\Windows Settings\Local Policies\Security Options - Network Security: LDAP client signing requirements = NONE - Domain Controller: LDAP server signing requirements = NONE

I've had to use it after SP2 however.

Are you using a winbom.ini?

CCC is the ATI Catalyst Control Center. MSSQL services are installed via OfficeReady, the way us OEMs pre-install MS Office. Its annoying too, can't even uninstall it properly.

Use DISKPART detail disk detail part detail vol list disk list part list vol make sure to select the disk, partition or volume before running any of the above commands. There is sometimes a delay before showing the information. It will also show you ODDs (Optical Disc Drives) and USB Drives when you use list disk. http://technet.microsoft.com/en-us/library/cc766465.aspx

Go into services.msc, find the Intel Alert Service and try to manually start it. It should give you an error there that you can read to get more information. And it will also log into the Event Viewer if it can't start the service and give more information. This service isn't limited to Viiv, but is also used by the LMS Service.

Updates: - The Old Ghostserver got its new RAID built, with no hot spare. 3 drives RAID1. Server 2008 Standard 64bit got installed but haven't gotten around to doing anything with it. - Our Server Lord has been complaining that his RDP session to VISTASERVER gets disconnected. I've been struggling with trying to figure out why. http://www.msfn.org/board/index.php?showtopic=124715 - Found out that Ghost won't put images into a certain folder anymore, complaining that the drive is out of space. That is totally wrong. I did a test and can put a WIM in that folder with imagex, so its limited to a Ghost issue. Unfortunately, we do not have a support contract with Symantec anymore, so we are going to just have to work around the issue. http://www.msfn.org/board/index.php?showtopic=124618 Imagex.WDS is experiencing all sorts of minor issues, all found while checking for audit events after turning on the account logon failure audit rules to troubleshoot the RDP issue. - Microsoft Windows Security, Event ID 4769 A Kerberos service ticket was requested. Account Name: IMAGEX$@WDS.LOCAL Account Domain: WDS.Local Service Name: krbtgt Service ID: NULL SID Ticket Options: 0x60810010 Failure Code: 0xe Unfortunately, this seems to be more of a generic message that gets recorded, although to be able to turn off the option would be great. A possible solution was to use auditpol to change the logging, but I haven't figured out how to use that program yet. - An IPsec Main Mode negotiation failed. Cause: no policy defined.... - The Windows Filtering Platform has blocked a bind to a local port. LSASS and SVCHOST connecting to ports in the 50,000 range, using protocol 17 (UDP). Windows Firewall is not enabled. I ran a port scanner, but it did something to the server, which it took the other virtual NIC in the team and gave it the same IP as the Team itself. End result was an IP conflict occurred, and the Team IP became the standard Automatic Configuration 169.258.x.x IP Address, which dropped DHCP to the domain. Since the team has a static IP, you can't release or renew the IP. I rebooted the server and it came back. I also tried another program but it was not recording the data properly. Still stuck on this one. Its annoying because there are about 3 events logged every second about this. - Kerberos Key Distribution Center ID 29. Smart Card requirement for authentication is enabled automatically. We don't use it and there is no Personal Certificate installed, thus I can't request a new one. http://www.msfn.org/board/index.php?showtopic=124740 - The network upload issue is sitting in limbo. We got permission to open a support ticket with Microsoft using the OEM Connect Channel, but something happened with our account and we can't log into the site... It seems the further I go into Server 2008, the more stuff I gotta fix...

You can run a setup from the WinPE 2.0+ but if you use a WINBOM you are going to need the old WinPE 1.5 or lower. Just call the install using regular setup.exe switches.