cluberti

I'd suggest using Wireshark to gather the trace (wireshark.com), but there are others.

The only thing you have to watch out for is wireless devices - they're set to "max performance" by default, and if your WAP supports it, they can be set to power saving modes and save a good chunk of battery time.

It will only recreate the file if you crash the box. Have you compressed and uploaded the memory.dmp file you created initially?

Well, since IPX isn't routable and IP is, it's most likely going to be a routing issue (I know, surprise that we have the issue at the router ). I'd say you probably simply have a router with some limitations in it's functionality.

Great! You learn something new every day .

If you create a new account to test, does the issue also appear for that account, or is the folder there?

You know, you could make a WinXP WIM file and install it that way...

Use the peimg command to add the network drivers to your boot.wim, then it will work. A pretty good writeup was done here: http://www.uvm.edu/~jgm/wordpress/?p=51

No, the installer is completely image-driven. No more winnt or winnt32, at all.

That's OK - but if you're using a pirated CD, you will get those errors. And hopefully the images in the link I posted regarding the script will help you do it right - if not, perhaps someone can translate for you. Language barriers do not bother us here at all, so no worries.

Unfortunately, it cannot. Again, I do believe that will change with the next server OS, but we shall see what RTM brings.

? I'm interested in performance and reliability, and those two products (believe it or not) work absolutely great on x64 if you use the right versions .

I think at this point we'd need to get a network trace from one of the machines while this is happening, to see what's going out and coming back over the wire.

First thing to try - does the issue occur when using safe mode w/ networking?

I don't understand - you're trying to update a memory.dmp file? Those are only created when a machine crashes - there's no update. I guess I'm misunderstanding what you're asking - perhaps you can clarify?

I prefer Symantec corporate or CA's eTrust product, but you'll get all kinds of responses to a question like this.

The problem is likely that you've actually run out of environment space in the DOS environment window. The default environment space in a command session is, I believe, 1024k (1MB) during Windows setup. If you are adding a lot of users, or calling external application installs, you can actually run out of environment space (remember, every application called by the command window runs as it's child, and shares it's environment space during Windows install). If you've rolled back your changes and the issue persists, you may want to create a new .cmd file and copy and paste the data from the old into the new and try again (I've seen wierder things before during unattend, and new files have fixed similar issues after rolling changes back).

Firstly, I'm not going to attempt to tell you how to fix your script - you are indeed doing it wrong, and it is documented in the Unattended Guide right here on this site how to do that properly (and very well laid out in pictures, I might add). Secondly, if Windows tells you that the OS is not genuine, then it failed the WGA check and your product key is either not being read properly or indeed is counterfit (generated by a keygen, or a "known" key that generates one of the many known "blacklisted" PIDs). You will need to contact Microsoft or the hardware vendor of your PC to get the issue resolved if you indeed purchased a legitimate copy of Windows. You will know you have a legitimate copy if you have a hologram or OEM-branded product CD, a Certificate of Authenticity, and a Certificate of Authenticity sticker with the product key listed on it (it should be affixed to the computer, but it can also come inside the product box or shrink-wrap). If you are missing any of those things (especially the CoA and CoA sticker), you will most likely not have a legitimate copy of Windows. If you know you have an illegitimate copy of Windows and are asking about how to get around the WGA check, here are the rules on that:

The school's network is likely not using Netgear 5-port switches, that back-end switching fabric speed matters quite a bit.

LOL

If you've added a boot image and an install image (you have to add both to the wdsutil), you should see your install images (you won't see x64 images added to the WDS server if you're running x86) after you provide your logon credentials.

Most everything you need is included in the WAIK: http://download.microsoft.com/download/8/6...5-LRMAIK_EN.img

There's no way to add the user account picture to W2K3. You can enable the themes service and get the XP Luna Themes support, but the pictures are only enabled if the "Welcome Screen-style" logon components are installed, which they are not in 2K3. Therefore, it reverts to the "Domain-style" or "Classic" logon options, sans pictures. I believe this to be different in Longhorn/Vista, but 2K3 does not contain the functionality to display these pictures (they're not part of explorer.exe, they're part of the fus/welcomescreen components in XP).

If you do a ping -a <ip_address>, it should do a reverse lookup and give you the hostname of the machine that DNS thinks the IP belongs to (you need a working reverse lookup zone on your DNS server for this to work, obviously). If you're talking about finding it physically, that requires either a diagram showing where it is either on the floor or which switch port and patch panel it's attached to - there's no automated way to do that. Not sure which you mean, but hopefully you mean you're just looking for the host name .

Is it profile-specific (meaning is it affecting all users), or just one or two users on the machine? Since this is usually profile specific, knowing who it affects will help.