cluberti

I guess the real question is, "why is it so hard for people to do things in moderation?". I know that there are always people who will be exceptions to this rule due to serious health issues, but for the vast bulk of humanity we'd all be healthier if we just didn't eat too much junk (it should be a treat, not a staple of one's diet), exercised regularly (even 30 minutes a day can't be that hard for everyone), and had a bit less stress and more free time to relax with friends and family. I was 250+lbs at 5'11" a few years back, and after I heeded my own advice I got down to under 200lbs, lowered my cholesterol and overall body fat, and I've reduced my stress at work as well (that last part was the hardest part, btw). I find I'm far happier now, and I'm not as tempted by junk food as much as I once was, because I've realized that there are meals out there that taste just as good or better, and are far better for my body. You only get one of those, so try not to screw it up too badly, I guess, is my long story short .

Roaming profiles are OK for laptop users, but you need to make sure you keep at least 2 or 3 cached copies of the profiles on those laptops if laptop users are going to have functionality off of the domain. As to specific GPOs, there really aren't any that would be specific to laptops, unless you write custom ADM templates to set something specific for laptop users. In short, no, there aren't any "laptop-specific" GPO settings you need to be aware of, unless you've generated your own ADM templates. As to the profile issue, I do suggest roaming profiles if users migrate to multiple machines during their workday or workweek, but if users generally have a single workstation, local profiles are generally better-suited. If remote storage of files is required in this case, redirecting shell folders is a decent way to make this happen. I'm not really a big fan of that, though, and it can be a real problem for laptop users unless done just right.

From what I understand, you configured your default profile location to be at \\server\users\, and when a new profile logs on it creates the \\server\users\%username% folder. You also have configured the %homepath% variable to point to \\server\usershomefolder\%username%, correct? Assuming the above is correct (or close to it), what you see is expected behavior. When a new profile is generated at first logon for a new roaming profile, it is always generated in the profile path (in your case, \\server\users\%username%\). The %homepath% variable is just a nicety - it's only used to set the home path or home drive location, nothing else. If you want the %homepath% or %homedrive% location to point somewhere in the new profile, you should really be setting that to \\server\users\%username%\Documents or \\server\users\%username%\My Documents\, for Vista or XP clients respectively.

Also, if you have a 2003 server you have access to, you can use the CMAK to create one.

If you tell them you had to replace the motherboard because it failed, they'll generally let you reactivate. If you've done this multiple times in the past, they may balk, but otherwise you should be fine.

message. After pressing OK appeared service's properties window. When I've pressed Start button appeared such: message. Service doesn't starts. Once you added the registry keys, did you restart the machine before attempting to start the services?

If you're using XP in a non-Domain environment, this is actually normal behavior. In this scenario, XP tries to do a limited logon of all accounts that are listed on the welcome screen, to see which one(s) require a password, and which do not. If you use the "classic" logon, this event won't be logged (either disable the welcome screen or join a domain), or don't audit failure for logon events. This is described in KB305822, and it looks like it won't be until SP3 at the earliest that it's resolved (although it doesn't happen on Vista or Server 2008, as far as I can tell).

Without the MSDE or SQL database that held the data about all of the stored updates, they are useless. If you have the susdb*.* database files from the previous install, you can go here to get a head-start on installing a new server with the old data.

Consider a security-filtered forest trust, assuming these are two different forests. You can read more about it here to start. If you're going to be the one implementing this, you definitely have some reading to do .

The disk time counter number is an average, yes. And the reason you see 160% is precisely because it's a physical disk counter - the OS knows via the driver that there are 3 physical disks there, so I would expect that 160% busy on a 3 disk RAID5 is approximately 50-60% busy across all 3 disks.

Not a problem - always glad to help, especially with the easy stuff

XP's support for 16bit applications was limited, and Vista's is even more so. You're emulating an 8086 environment running 16bit code on a 32bit OS, which is very likely running on a 64bit processor. It isn't going to go well, especially with Vista x86 having very limited 16bit support (and of course no support for 16bit apps that require hardware access - you might be able to make it work with virtual devices or mapping trickery, but that's not a very good long-term solution). I expect that, since 16bit support on Microsoft platforms has existed since the days of Windows 1.0 in 1985 (and 16bit protected mode in Windows 3.0 in 1990), and the shift to entirely 32bit applications was done in Windows 95 in 1995, that 16bit applications (DOS or Windows-based) should not be expected to run on a new OS released 4 versions (NT4/2000/XP/Vista) and 12 years later. Also, with Vista and Server 2008 likely being the last 32bit OSes from Microsoft going forward, finding a 32 or 64bit replacement for that app would be wise to do soon. I know that most of these applications are likely not easily replaceable, and for that you're stuck with Virtual Server or Virtual PC. Honestly, I find that Virtual PC running my 16bit applications on XP x64 or Vista x64 work great, and are a good solution. If you need something more enterprise, consider Windows 2003 x64 running Virtual Server 2005 R2 SP1.

Do you have the \lanmanserver and \lanmanworkstation keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services? If so, do they match another (working) machine of the same OS and service pack?

I'd say it would be wise to gather a process monitor log of the install sequence during a "fast" install of an application, and another of the same application (preferrably on an identically configured OS/drivers/apps) when it's "slow". It'd be very interesting to see what registry and disk activity exist during the "slow" and "fast" installs, and how they are different.

You can go over 100% busy on a RAID array, but not usually a single disk. Also, are these Logical Disk or Physical Disk counters? One last thing - one snapshot every 5 minutes is a pretty large gap, so is there any reason you didn't go with 5 seconds over 24 hours and a 250 - 300MB log file?

It ships with the OS (note those are Vista screenshots). He can't uninstall it.

The only thing I can think of then is to check the event logs - any warnings or errors relating to LSASRV, USER32, SRV, Winlogon, LSASS, etc?

Emphasis mine. Windows 2000 entered extended support almost 2 years ago - as such, non-security hotfixes require a premier contract with extended support for the product to receive the hotfix.

Moving to Unattended Vista forum in the hopes this will get more views/results.

Hmmm..... Does it happen for all users, or just the user represented by SID S-1-5-21-3752391563-857441031-2975066921-1000?

It does - you need to set the paging file size manually to 1533MB for both min and max values, and make sure the dump is set to "Complete". Once you've done this, reboot and your keyboard dump should work. The only other thing that can stop this are drive encryption applications (including bitlocker).

Is the minimum and maximum size of your page file set to be at least RAM+50MB? Also, is your paging file on the boot volume (the same volume as the \windows folder)?

You can use a logon script, but a better way would be to configure the site to zone assignment list in Group Policy and put those sites in the restricted sites zone. Why do it the hard way with host files?

Regular, mainstream support ends in 2009 for Pro. Extended support (paid extended break/fix, free security updates) continues for 5 years after that, or 2014. For reference, Windows 2000 is currently in it's Extended support phase, and will be until sometime in 2010.

Well, honestly, at that point I start pestering the vendor to see why this happens with 64bit software on a 64bit platform, because only they'll know how the solution is architected. This is internal code problems, not an OS problem at this point.