If you are using a domain environment with roaming profiles or home directories that are located on remote machines (servers) and experience slow log-on process this is probably because Windows 7 and Windows Server 2008 are configured not to detect to which Windows Domain Controller they belong to by default.
Here's how to speed up the logon process on Windows 7 machine. (Probably will apply to Windows XP too).
When you try to remove a PC from the HomeGroup on Windows 7, you might receive error.
When you run the troubleshooter, you might receive the following problem:
Problems found: Peer Networking Grouping service isn't running
To solve this error, please do the following:
Delete the file:
that is located in the following path:
When you paste this line in the RUN windows you might receive the Access Denied error.
For some time now I had a lot of issues with my PCH-A210.
When I power it on, I check the network settings and PCH-PopCorn Hour aquired an IP address from my router. No matter that I can ping it I am unable to access my PC (myiHome server running normally).
When I try to browse the PCH folder structure using UNC path I can usually start navigation, but after one or two subfolders it stucks with the network discovery line slowly crawling. After some time folder opens, if I try to go even deeper in the folder structure I usually get an error about 'network path not found'.
I was not sure sure if this was related to firmware update (latest one) or this PCH-A210 is just one buggy device.
To fix this problem, I had to restart the damn device 5-10 times until I'm able to normally browse the folder structure and copy from and to the device. Unfortunately I haven't received any help from Popcorn Hour forums so I was on my own. I've managed to find out the culprit of the problem that was located on my desk.
Today we had printer issues with some of our Citrix servers in the XenApp v5.0 farm. Printers were not automatically mapped in Citrix session.
We have discovered that Print Spooler was stopped on those Citrix servers. Once we started the 'print spooler' service the problem wasn't solved.
We have checked the System Log on one of the problematic Citrix server and we discovered that the Citrix Print Manager Service was stopped also because this service depends on the Print Spooler service.