Tripredacus

The user PMed me to say that the second domain controller is indeed a backup for the primary domain. What is the error you get with the certificate autoenrollment?

Its actually sysprep but you should look here: http://www.msfn.org/board/Customizing-Windows-f40.html

OK so you can see the wireless connection, Do you get an error when you try to connect to it? By default, Windows will automatically connect to the first available unsecured wireless connection. If there are no unsecured wireless connections, it will not attempt to connect to any of them. What happens when you try to connect to yours?

That is indeed the option for XP but Vista's menu is laid out differently. Also, after changing to Large or Extra Large Icons, there is a period of time before the icon changes from the default picture icon to a preview of the image.

The driver file is typically an INF file that installs other support files or writes to the Windows registry. The INF file can be opened in notepad and pasted easily. Which model of EEE PC is it? Also, there is no "driver" provided by Asus for the USB camera. Its functionality is provided solely by the OS, in your case, Vista. So if it is not installing, then you must have left out the driver that handles that. Also, make sure that your BIOS is set for "install" mode (instead of finished, or whatever the two things say) and make sure the camera is enabled in the BIOS as well. We found that if the camera was disabled in the BIOS, it would still be detected in Windows, but Windows couldn't install the driver for it because the hardware wouldn't be able to send a successful start response because it was disabled.

Sorry, it looked like you did a fake edit. I forget that this forum has an edit delay before the note shows up on the post.

You're a funny guy there.... Well Windows is detecting that there is a disc in the drive, it just thinks it is a blank DVD-R or RW. If I put in a movie, it prompts me to open it in the CD Writing Wizard.

We do/will not use WDS to deploy to corporate pcs, ie workstations and servers within our company. We got this understanding: WAIK is to deploy within your own company OPK is to deploy onto machines that are to be sold/redistributed In addition to using WDS with the OPK, we are also able to make product recovery media with it.

Well, it works great for us here when the base PC is an ACPI PC. i think we all agree the script will work as anyone who is updating their HAL in their XP image is doing the same thing, Iceman was just pointing out the specifics. back to the original post, Go download the Microsoft deployment Toolkit and the WAIK, you will be able to create both XP, 2003, Vista and 2008 based images from that tool, it will also intergrate into SCCM if you are looking to move to that from SMS Thanks I've already used the WAIK but our MS rep told us we can't use that anymore. So I am switching to OPK instead because of our licensing. It works the same. I've got a handle on Vista and 2008, but we get the choice of moving from Ghost to WDS for XP and I'm trying to make sure it will work out properly once we switch. The only issue I have with XP on HALs is the following: We create XP images on a per-board basis, not a big mess of boards. So the only thing we will see in a different cfg with one image is perhaps a Celeron vs a Core 2 or on the other side a X64 vs a LE1620. Either way, the CPU is the only thing that will change. All of the boards we use are set up as ACPI. The deal is that XP Pro SP2 detects the HAL at the start of Windows loading so it won't crash if you change the processor out. Of course the original image needs to be made on a UP, because it is designed to scale to an MP if it detects a CPU change. This is what is noted in the KB article I posted above under bullet 4. I also tested this using identicle configs except for CPU type. Install everything on the PC with the Celeron (including drivers and apps). Make note of the HWID in Devmgmt and the full HAL name given. Turn the machine off, take out the HDD, put it in the machine with the Core 2, boot up and compare against the HAL again. It changes to the MP HAL with no errors to be found. So this is why I am wondering why it is even needed to change the HAL after imaging, or even have multiple images for different HALs in this case. Yes I understand the need for this if 1) you aren't using similar hardware 2) you aren't using XP Pro SP2 or newer. But since XP can autodetect the HAL, you should be able to use the same image for either MP or UP case. Of course you couldn't use it if you disabled ACPI or tried to put it on an IA64 or what have you. Anyways its lunch time for me. Let's talk about this some more eh?

It sounds like the M5410 was a BIOS setting away from being the latter.

If some machines work and some don't, you may need to update the BIOS on the ones that don't. Or if they have a Boot Agent, check in there also.

I don't think the DHCP cpl is natively able to do what you are asking. I'm trying to think... I know that WDS has a function where you are given the ability (if you enable it) to approve all BOOTP requests from specific machines, but the DHCP cpl doesn't seem to have it. You should just manage your asset inventory by keeping record of all computernames and MAC Addresses. All the companies that I have dealt with that uses this type of "permission required" DHCP all run it that way. They use network discovery to log all new machines, and the admin has to approve them (or adds them manually or imports from new inventory spreadsheets) before they can get served an IP address. Of course this specific example is used via Altiris Notification Server.

Is the second domain controller on the same domain, and acting as a backup? Or is the second domain a totally different domain name?

You do not see any wireless networks in the cpl? Is the wireless service enabled? Is everything hunkydory in device manager?

On the top, click the arrow next to "Views" and choose large or extra large icons, whichever best suits you and your resolution.

Nevermind... I found it in the BIOS.... I did try memtestx86 earlier and it was saying the timing was 1-1-1-31... But the BIOS showed more reasonable timings...

That's not really an "upgrade" now is it?

I will definately take a look at those two possibilities once I can get approval to start working on it again. Does memory timing have any effect on the image at all? And if so, is there any documentation or editorial anywhere online I can find to view its effectiveness/non-effectiveness?

Is there any programs out there that can run in Windows that will show the timing of the RAM in ns? We have a few models that aren't listed online yet that we use, so I can't get this information.

I've been having problems with my DVD drive recently. Its a Lite-ON ATAPI 16x +/- DVD-RW Dual layer drive. Suddenly, here is what it is doing: 1. Sees burned DVD-Rs as blank (such as my OPK 1.1 DVD). 2. Sees retail movie DVDs as blank* 3. Is able to read and launch PC CD-ROM game NHL06. 4. Is able to read and launch PC DVD-ROM PCGamer DVD from Zombies issue. 5. There are 3 region changes left, currently on Region 1. PC info: XP Pro VL *movies tested: Total Recall, Tomb Raider: Cradle of Life, Transformers Season 1 Disc 1. All three play in PS2. The region changes were caused previously because I have some Region 2 Transformers DVDs I watched a year ago or so. Also, this drive has already started exhibiting the "Eject of doom" issue that Lite-On drives seem to have. For example, my computer at work has a similar Lite-On drive, and it never ejects unless I use the paperclip. It has no problem reading discs. All Discs work in other players, like the PS2 or my work computer. I haven't bothered cleaning the drive because it can read other discs just fine. If anyone has any ideas, let me know.

You could switch up to XP 64bit to see that extra RAM, or use WIndows Home Server.

Do you mean the box re-checks itself and you see it doing that, or that you make the change but when you go to a folder you can't see any hidden files? Are you using XP Pro or Home, and also are you on a domain or was the machine previously on a domain, or are you logging in locally?

You can at least create an EFI partition with the PE, but I'm not sure on how it all works together. Maybe this article will give you some ideas. http://support.microsoft.com/kb/883390

A debate seems to have come up at my company regarding how we can't use images any longer (with Ghost) because of the different HALs in a system configuration. It seems we have gotten official word from our tech rep at Microsoft about this issue. However, this is in contrast with what is in KB309283: http://support.microsoft.com/kb/309283 Which says that if ACPI is enabled, XP will automatically detect the correct HAL. But if it ends up being true that we cannot use images any longer to deploy our machines using Ghost, then I do not see where there is a difference between that and using the WDS and WinPE. With exception of Vista, you have to capture an existing XP image as a WIM, which basically makes it the same process as Ghost. Someone tell if I am wrong or there is another way.

Don't rule out your CD drive also. Do you still need a LAN driver?