cluberti

This is true - perhaps if we knew what the problems you are seeing were, and the extent of these, we could help you clean it up. Moving from one domain to another isn't necessarily the wisest thing to do (although your move would likely not be difficult due to such a simple domain), nor is it necessary.

I'll point you to the "Unattended Guide" linked at the top of each and every page here - the answer is in there. Also, visit the unattended sections here if the unattended guide doesn't answer your questions.

"Remote Assistance" is the RDP method of connecting to a desktop like this, but unless you configure group policies, it isn't an automated process (someone at the remote end needs to basically click "OK" to allow the connection otherwise).

If you hibernate, you should see a screen similar to the boot screen telling you that the machine is hibernating, and then the power should go off once that is complete. If it gets "stuck", that's definitely a problem. However, there's a hotfix for this that you can request online. If that doesn't work, it's most likely your network adapter (or in the case of wireless, also possibly the wireless access point or router) causing the issue.

Vista no longer uses the same boot loader and boot process as XP/2003, so if you plan on having XP and/or 2003 on your system, you should install Vista after installing XP and/or 2003. If you are in the unfortunate scenario of installing Vista first and then trying to get XP or 2003 to work, you can follow this post to get it working. If you install XP and/or 2003 before Vista, you should have no problems at all.

Right - it's complaining that the RAID array is broken (which it is). Also, previously you stated that when you first saw the message the drives were in need of re-sync, which would also indicate inconsistency in the array which Vista would also have picked up on as a potential hard drive problem. It's not a false error, it's Vista telling you there's something wrong with the array, and heeding the message is probably a good idea .

It could have something to do with the fact that the XP CD you have was meant to be installed on a Gateway. Oh, and what you're doing isn't legal, either - that copy of XP is only meant for the machine it was purchased with. If you acquire a valid retail or OEM retail copy of XP, you'll probably have much better luck. Sorry I can't help further, but we can't assist you in violating the EULA for XP, it's against rule #1 of the forum rules.

Assuming you bought a retail package that contained both the x86 and x64 CDs, you may be able to format and reinstall using the x64 disc, and reuse the key. Activation may very well fail initially, but since you have a retail copy and are moving the license from the x86 install to an x64 install on the same machine, it should be OK. If you have an OEM copy purchased with your computer, however, you don't really have that option.

Did you follow these instructions yet? It's not as simple as popping in a CD and installing.

If you do it at the domain level for group policy (and not the machine level), she won't be able to modify it. Just be careful - software restriction policies are somewhat dangerous if you don't know what you're doing.

Probably when it's done, I'd guess. Seriously, though, a service pack just can't screw things up (like, say SP4 for NT4), so this has to bake as long as it takes (as with any release from Microsoft now) until it "just works". Even then it is sometimes not enough, but you can only be so careful I guess with projects this big. As to releasing it earlier, there are some reasons for this (and yes, Vista is one).

Unfortunately, blocking MSN messenger is tough - especially when the user is an admin on their box. You can't disable the later versions via the registry hacks (they no longer work), and you can't easily block ports or hosts (hosts change periodically, and MSN messenger can use port 80 to communicate). If you do not have a proxy that requires authentication to get out of your network to the internet, or do not have a firewall that can block traffic by sniffing at the application layer (Like an ISA firewall, for example), you're pretty much SOL unless you want to pay for software to install on that box (and she can uninstall, as well, as the admin of the box). If this is the case, I think it may be time to start gathering your data and bringing it up with the boss(es). If that doesn't work, you might consider living with it, or finding a different tact to approach this (or a different job).

If you click on Tools > Internet Options, how many URLs are listed in the "Home Page" box?

I plead the 5th .

Yup, MSDN/Technet this month.

You would need a DHCP relay agent for each subnet, and when that server gets a discover packet from a client it would forward it to the DHCP server. The DHCP server needs to have a scope defined for each subnet on which addresses to give out based on the requesting agent, and that is what I believe you are looking for. A quick google search should help you out here.

The beta for XP SP3 is still private, so legally you would have to be part of the private beta (usually being a beta Microsoft customer) or a Technet or MSDN customer, and you would then download it directly from MS. Please don't ask for links to download this, thank you.

Are you currently running validly licensed Office XP or Office 2003 on these machines? If so, what is the problem - you install the Office 2007 copy over the existing Office install, and provide the Office 2007 license when prompted. Or are you not running any version of Office, and trying to install the Upgrade of 2007 without a previous licensed version already installed?

Any particular reason you want to do things the (really) hard way?

Are you sure it's a false message? Also, could you post a screenshot perhaps so we could see the error?

Are you running the "Vista Basic" theme, or the Vista Aero theme? You can see this in the display properties under "Themes".

Note that since it's a GDI+ error, it could also be a poorly-written printer driver too - just throwing that out there.

The first two numbers are memory addressess that denote the location in virtual memory in the application's virtual address space that the instruction that was executed was stored (in your example above, it was at 0x4ec95695) as well as the location of the memory that was referenced by the request (again, in your example, 0x4ec62ef4). These will always be different every time you load the application, so these will always change and that is normal. The third number is the error code that was generated, and it's a Win32 error that states that there was a device I/O error that caused the problem. This would indicate that there is either something installed and hooked into the explorer process causing the issue, or perhaps a driver issue (either a filter driver, like antivirus / firewall / antispyware / backup software, or an actual device driver like the video card device driver). If you download and run ShellExView and disable all non-Microsoft entries listed, and then download and run Autoruns and disable all non-Microsoft entries there as well and reboot, does the problem return?

Not sure, but if you change the view the way you'd like for your folders, then use the "Apply to all folders" option in the Folder Options dialog box, does that resolve it for all folders?

That's a bigger problem, because you cannot disable just the favorites icons (although you can disable the Home | RSS | Print | Tools | etc portion of the command bar). You have to disable the entire command bar, which removes the favorites icons, tabs, and the icon section of the command bar as well - here's the reg change for that, and once you add it and open IE, you'll see what I mean: Key: HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Toolbars\Restrictions Value: NoCommandBar Type: REG_DWORD Data: 1 Since you likely want to have some Citrix icons in the command bar, this probably isn't going to help you.