cluberti

Yes - do not forget the /interactive (or /i, same thing) switch when creating a job with an active window you'd like to see. Otherwise, it won't be able to interact with your desktop session, and of course without a shell and most registry entries available to them, most applications will silently crash .

Most NICs are, but you can usually tell by going into the properties of your NIC in device manager or looking it's model information up on the internet. As to Linux, it depends on the distro, but QoS can be managed a few ways on Linux (I personally prefer this, but again, there are probably more ways than I'm even aware of to do this. Sounds like you need to do some more research on your own before diving into QoS .

I am indeed.

I've run so many darned builds I've forgotten what is what. So, I post RTM - if you're running a previous version, I'm bound to not know what you're looking at. Glat to have someone point out one of the few things that didn't change over the builds .

I wasn't speaking to that specifically - you can use any CD of the proper type on any machine with that type of install (retail, OEM, royalty, VLK), and it's in that grey area of the law (at least in the US). What I was speaking to, however, is the fact that you are not specifically supposed to use a retail or "retail OEM" CD as an unattended source disc (and technically not supposed to use royalty media if you aren't the royalty OEM). but it can be done. That's all I was saying.

Hm - when you created your primary image, did you do it on real hardware, or in a VM? Also, if you did it on real hardware, did you install any drivers before imaging the box? You can probably see where I'm going here, but I gotta ask...

Yes - with the above configured (and a reboot performed), you should be good if an error occurs the next time. The memory dump should be about as large as the amount of RAM in the machine (it's a complete memory dump).

I don't have an RC2 box anymore, but in RTM there's a checkbox in the Window Color and Appearance window called "Enable Transparency".

One other thing I forgot to mention - your NICs need to be 802.1p compliant. Once QoS is installed on your server (and your server and clients all have the QoS Packet Scheduler enabled, you should be able to configure things on the server via the QoS Admission Control snap-in. Give this link a read: http://labmice.techtarget.com/networking/qos.htm

First, make sure that your paging file is at least the size of physical RAM +50MB or so. In fact, make sure to follow these instructions, and then let me know the next time you get a memory dump: 1. If you have a feature like Compaq's Automatic System Restart (ASR), please disable it. This setting is usually found in the BIOS. With this feature enabled, if the BIOS does not detect a heartbeat from the OS, it will restart the server. This will interrupt the dump process. 2. Create or set the following registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters Value: CrashOnCtrlScroll Type: REG_DWORD Data: 1 Refer to the following Knowledge Base article for more information on this registry key: 244139 Windows Feature Allows a Memory.dmp File to Be Generated with Keyboard http://support.microsoft.com/?id=244139 3. Right-Click on the "My Computer" icon on the desktop and select "Properties"; this will open the "System Properties" window. Go to the "Advanced" tab and click "Performance Options". Click "Change" under "Virtual Memory". Set the pagefile to be located on the partition where the OS is installed, and set it to be equal to Physical RAM + 50 MB. 4. Also in the "System Properties" window, click on the "Advanced" tab, then click "Startup and Recovery". Make sure "Complete Memory Dump" is selected (see 4a if this is not in the list). You can change the location of the memory dump file to a different local partition if you do not have enough room on the partition where the OS is installed. 4a. If the "Complete Memory Dump" option in step 4 is not available, you will need to manually set this registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl Value: CrashDumpEnabled Type: REG_DWORD Value: 1 5. You will need to reboot the server for these changes to take effect.

But that was beta code (RCs are more final, but still beta). It cannot be considered wierd that something that wasn't supposed to work worked in a beta, but was "fixed" in RTM .

At my previous employer years ago we tried to keep it 1 per 100 PCs, but it ended up being more like 1 per 200 PCs. At least we tried, and were able to hire more at times .

I second the IEAK suggestion, as this is the supported way of adding certain changes that otherwise get reset after a new user logs in.

If you install a clean version of the OS off of the install media (not the image) and install the drivers on that, do you get the same behavior?

Unless you're using an inbox driver (in which case this is wierd), providing a 3rd party video driver to install during setup can cause this behavior if they're checking for connected monitors during their install routine. This behavior is fine during a running Windows session, but because we're not totally installed when this happens during the setup routine, you get these prompts. If you remove your video driver from your setup routine (and thus install the base VGA or inbox video driver for your video card), the problem will likely go away. And there's not much you can do to fix it either, as it's a driver issue.

The other part of the equation is that only the royalty OEM and VLK versions of Windows are designed and supported to be installed in this manner, and only the royalty OEM is supposed to be able to configure the OEM unattend. It can be done with non-VLK media (as noted here many times), but it ain't easy .

RTM setup checks the amount of RAM in the machine. If it's less than 512MB, it won't install - the check fails, it says so, and you don't continue. However, you CAN remove memory once installed to actually run Vista on a machine with less than 512MB of RAM, but you'll not be able to actually install Vista on said machine until you have 512MB of RAM installed during setup.

The question should be - what kind of things do you WANT to do. If you can answer that, we can tell you if it's possible to do said "thing" without the XP machine joined to a domain.

It would also help to know what the actual problem is that you are seeing. There are many problems you could be having with printing from an application, but we can't guess which from the data you've provided. Please be more specific so we can help.

Not perhaps, QoS will help. But you need to understand how it does, and does not, work. http://technet2.microsoft.com/windowsserve...logies/qos.mspx http://technet2.microsoft.com/WindowsServe...3.mspx?mfr=true Read the overview sections, the sections about Differentiated Services Code Point (yes, it's related, and yes, you need to understand it in at least basic terms), and use the links for the other QoS tools and resources you might need to get started.

Because you have not only the actual text-mode setup executive to load, but also the TCP overhead in startrom.com to load (otherwise it wouldn't work very well over the network if TCP and the basic NIC driver failed to load ). Therefore, there's just slightly more overhead in RIS, and thus the actual Windows setup routines have a bit less low memory to load into (and that's why we check for that in the bootstrap). When you use a CD, you aren't loading the extra few K that a RIS or WDS-based install does. Have you also considered setting up a test server in a lab running RIS (with no images configured other than the default), and see if the same machine gets the same error against that server?

I believe you would - unless you use WinPE or BartPE to determine what type of machine it was first. That'd probably be messy though on a single CD install (something that could be done easily over RIS or WDS though).

If I'm not mistaken, that's an SMTP error, and it's not a Symantec error. It's just relaying the SMTP code sent to it by the upstream mail server - which means you'll have to contact your ISP to send out a mass-mailing (they probably view it as spam unless you tell them otherwise).

Moving to more appropriate forum.

Does your site structure span offices, towns, states, countries? If you only have a smaller environment, that will work just fine. However, if you've got a multinational organization, something like <country code><state/province/city><laptop/desktop><designation>. For example, an XP desktop in NYC in the US in marketing would have a name like: USNY1LMARK01 Just my few quid.