Some Notes on the Machines

Try this:

http://support.microsoft.com/kb/2537096

‘spfarm’ is also involved in the errors. This appears to be an unresolved bug in SBS versions after 2003.

“Autoruns”:

http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

is the most complete of all.

Try the registry merge here:

http://www.sevenforums.com/tutorials/197908-power-plan-specify-default-all-users.html

The one under the caption “To Allow Users to be able to Specify Their Own Power Plan”. Tried lots and lots of things, this worked. Its contents are below. After the merge you may have to log off and on or even reboot, before the fix will be operational.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings]
"ActivePowerScheme"=-

It has to be installed:

http://support.microsoft.com/kb/969708/en-us

Excellent instructions here:

http://www.itquibbles.com/sql-sbsmonitoring-high-disk-usage/

What is needed, in sum, is to rebuild the SBSMonitoring database.

The simplest commands to take ownership and give full permissions to administrators:

takeown /f directory_name /r /d y
icacls directory_name /grant:r administrators:F /t

The above is recursive, through all files and folders in the tree. If recursion is not desired, remove /r and /t.

If you have a problem with COM port devices under Windows 7 or later, your system may think it has autodetected it as an old-style RS-232C port mouse! To fix that, regedit here:

hklm\SYSTEM\CurrentControlSet\Services\sermouse

and change the DWORD Start to 4. This prevents the autodetection of COM-port mice!

Contributed by the excellent Brad Hollingsworth.

If a PC can browse the web but cannot see Windows shares, and/or the NIC is red-X’d in the tray, check the “Network Connections” service: it should be set to Manual, but it needs to be running, and if it’s not, you have the problem which I am writing about here :-) This is known to work in Windows 7, according to web resources it appears to be good for others as well.

1. Open an administrative command shell, or run these using CMD in a remote management tool like Labtech.
2. Run this: sfc /scannow If it says it fixed anything, reboot, and if all is well you’re done. If not:
3. Run this: netsh winsock reset & shutdown -f -r -t 0 The PC will reboot. Check again. If not done yet:
4. Then run this: netsh int ip reset C:\ipreset.log & shutdown -f -r -t 0 The PC will reboot again.

If not done yet, let me know what you did to fix it!!!

Here is a simple procedure for CMD, it works as long as the queue location was not changed:

net stop spooler
del /F /Q %systemroot%\System32\spool\PRINTERS\*
net start spooler

On SBS 2011, you may see this repeated a lot in event logs:

Session "WBCommandletInBuiltTracing" failed to start with the following error: 0xC0000035

According to Microsoft, this can safely be ignored. However, many times these events will crop up so often as to eat up server performance.

To fix, open an administrative command prompt, CD a la:

cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN 

and run

PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

If you see a message which says SPWriterServiceInstance would not start, and/or if the Sharepoint VSS Writer service is disabled, try this:

stsadm -o registerwsswriter

which should get the VSS writer set up and going, and then run the PSConfig above again.

References:

http://timaddamz.wordpress.com/2013/08/27/sbs-2011-session-wbcommandletinbuilttracing-failed-to-start-with-the-following-error-0xc0000035/

http://social.technet.microsoft.com/Forums/en-US/4092f3fa-7bf8-4194-bc78-9cfcdf6f058b/sharepoint-2010-vss-writer-service-disabled?forum=smallbusinessserver

http://social.technet.microsoft.com/Forums/en-US/94c5f178-f020-4d0f-ba7c-11c415d0d862/manually-running-psconfig-is-required-after-installing-sharepoint-foundation-2010-updates?forum=smallbusinessserver

http://msmvps.com/blogs/bradley/archive/2011/06/30/remember-you-must-run-psconfig-after-sharepoint-sp1-is-installed.aspx