Some Notes on the Machines

RWW often freezes and fails. Happily, the amazing Jared Dexter found a fix: when memory usage reaches a certain high degree, IIS refuses to cooperate, and we can change this. In an administrative CMD:

1. CD to %ProgramFiles%\Windows Small Business Server\Bin\WebApp\RemoteAccess
2. Open the file web.config, using Notepad
3. In web.config, search for item <serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
4. Change the item to <serviceHostingEnvironment aspNetCompatibilityEnabled="true" minFreeMemoryPercentageToActivateService="0" />
5. Save and close
6. Run IISRESET.

The above is summarized from:

http://blogs.technet.com/b/sbs/archive/2014/01/13/troubleshooting-an-unexpected-error-occurred-message-when-using-remote-web-access-to-connect-to-computers.aspx

Interesting material here:

https://msdn.microsoft.com/en-us/library/windows/hardware/dn529134

Here is a comprehensive document:

http://www.omegaits.net/articles/configuring-folder-redirection-in-windows-server-2008-r2

Windows Firewall is required, if network-shared printers are to be used, in Server 2008 R2 and Windows 7. See here:

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

But there are still many instances where Windows Firewall gets in the way. In these cases, set up a Group Policy for Windows Firewall with Advanced Security:

Computer Configuration,
Policies,
Windows Settings,
Security Settings,
Windows Firewall with Advanced Security,
Windows Firewall with Advanced Security – LDAP://cn={GUID},cn=….

and Allow all connections both inbound and outbound. That way the APIs all run, but no interferences.

In addition to installation of the Quickbooks server piece, folder permissions have to be set correctly. Make sure you use the Advanced permissions settings area, and choose “This folder, subfolders, and files”.

The program folders have to give full control to “Users”:

http://support.quickbooks.intuit.com/support/Articles/SLN76845

and the data folders have to give full control to the service users created during installation of the server piece.

http://support.quickbooks.intuit.com/Support/Articles/HOW12213

Excellent instructions here:

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

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

Here’s a great step-by-step, using the ‘netsh’ command:

http://www.windowstricks.in/2009/06/how-to-change-subnet-mask-of-dhcp-scope.html

If you see a bunch of these:

SpoolerWin32SPL, Event ID 4
“The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-18\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable.”

look for S-1-5-18\Printers\Connections in the registry. It probably goes down as far as “Printers”, but “Connections” is probably absent. Create it as an empty key, and the messages will stop.

If an NTFRS service restart does not bring back the domain controller capability, if the SYSVOL share never comes back, the Jet database may be corrupted. This database will be automatically recreated if you do this:

1. NET STOP ntfrs
2. Rename the folder “C:\windows\ntfrs\jet” to jet.OLD
3. NET START NTFRS

The following command set appears to be able to perform a major refresh/upgrade/update to Sharepoint:

C:
cd \Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin
stsadm -o provisionservice -action stop -servicetype spwebservice -servicename ""
stsadm -o provisionservice -action start -servicetype spwebservice -servicename ""
psconfig -cmd upgrade -inplace b2b -wait -force 

I found that after running the above, I had to add binding ‘http://companyweb’ in IIS, on port 80.

In addition, the following pages seem to contain info for use when companyweb is not working:

http://davidcmoisan.wordpress.com/2009/05/08/sbs-2008-solving-four-sharepoint-problems-at-once/

http://forums.techarena.in/small-business-server/662096.htm

http://www.vistax64.com/sbs-server/272630-companyweb-has-gone-missing-sbs-2008-standard-sp2-sharepoint.html