Tripredacus

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?

I've never tried using that part of the software before. I recommend you contact Nero support. I also looked and I just kept finding your cross-posts for the most part. The help file doesn't help much. I've had good results with Nero support, perhaps they can help you out.

Are you using anything that can push an app to a client, like SMS or Altiris? Does your clients use a login script?

SOrry. Please list what you have tried so that finding a solution may be easier.

Yes, maybe search the forums? http://www.google.com/url?q=http://www.msf...WzgGjzhOLjQDrTg

OK that page has the following steps: 1. Remove previous flash player versions. So check your add/remove programs. Oh try this link to the ZIP to install it. http://www.adobe.com/support/flashplayer/t...r_9_ActiveX.zip Here's the page with the instructions. http://kb.adobe.com/selfservice/viewConten...6&sliceId=2

I think the reason why it is difficult to find license information regarding virtualized XP is because it wasn't part of the EULA. There are 2 things I have been able to determine: 1. You can use XP Pro on a VM if that XP is not running on the host or another PC. In other words, the CD Key for that copy of XP cannot be in use on any other machine or VHD. This idea is covered in the Transfer Rights portion of the XP EULA. 2. You can use XP Pro (or 2000 Workstation but not both) on a VM hosted by Vista Enterprise, as this is covered under Vista's downgrade-rights initiative. Pre-Vista virtualisation FAQ http://ncsu.edu/software/agreements/virtualfaqms.php http://www.vmware.com/files/pdf/windows_vecd.pdf

There are different stop dates for different distros of XP, which is why you are seeing multiple dates. I don't have a list of them but the different versions are OEM, Retail, Volume License, etc. You'll still be able to buy XP in stores (retail version) after the final day because that day is sale date. So stores may still have copies floating around to get. Oh also, you should be able to get the Vista downgrade-rights XP for a little while to come also. edit: typo

I've seen this a couple times but it has been cured by a reboot. if that fails, turn off the automatic updates. It should stop it from trying to update.