# Friday, December 01, 2006

Trying to run the Group Policy Results Wizard in SBS 2003 from the server to a remote PC gives the following error message:

Group Policy Error
Failed to connect to <computername> due to the error listed
below. Ensure that the Windows Management
Instrumentation (WMI) service is enabled on the
target computer, and consult the event log of the
target computer for further details.
Details: the RPC server is unavailable.

Needless to say, WMI and RPC server are both running on the target computer and the event log contains no entries.

The Microsoft solution is to enable "Allow Remote Administration Exceptions" in the Small Business Server Windows Firewall GPO (Computer Configuration | Administrative Templates | Network | Network
Connections | Windows Firewall | Domain Profile).

Naturally this doesn't help any.  A helpful post by DonL on Microsoft's public SBS newsgroup gives the fix:

The RPC port 135 is being blocked - by the Microsoft Firewall Client for ISA
2004. To unblock, do the following:

Go to ISA Server Management
Browse to "Firewall Policy"
Select "Edit System Policy"
Browse to "Active Directory" under "Authentication Services"
Uncheck the box titled "Enforce strict RPC compliance"
Click OK
Apply the new settings



Friday, December 01, 2006 6:36:50 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Monday, November 27, 2006

set allowallpaths = trus

set allowremovablemedia = true

set allowwildcards = true

bootcfg /default, /add, /rebuild, /scan, /list






net use [\\ComputerName\ShareName [/user:[DomainName\]UserName] password] | [drive letter:] [/d]


sbs | win | xp
Monday, November 27, 2006 10:50:56 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Sunday, November 12, 2006

Go to Regedit:

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

Data Type: String Value // Value Name: RegisteredOrganization
Data Type: String Value // Value Name: RegisteredOwner

SFC Source change is at same location "SourcePath"

See MSKB 222473

win | xp
Sunday, November 12, 2006 3:29:35 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Tuesday, July 25, 2006

To get the lady back without reinstalling take the following steps:

Delete camcurve2.bin from C:\Program Files\Nikon\NCapture4\Control and the original image will be restored from camcurve.bin.

Tuesday, July 25, 2006 9:45:24 AM (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Tuesday, May 09, 2006

Well after a bit luck I have found a solution that was quite simple. I tried this once before but did not save (overwrite) the new selection - it worked perfectly this time:

Use NTbackup to remove Recovery Storage Group reference from the backup selection script.

a. Start -> Run -> NTBackup -> Advanced Mode -> Backup tab -> Job -> Load Selections.

b. Select Small Business Backup Script.bks

c. Click OK on the error message:
"Some invalid selections found in C:\Program Files\Microsoft Windows Small
Business Server\Backup\Small Business Backup Script.bks".

d. Job -> Save Selections (overwrite --> Small Business Backup Script.bks)


Who knows, have to try it on offending client's box soon.

Tuesday, May 09, 2006 11:26:18 AM (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Monday, April 03, 2006

Microsoft today (3 April 2006) a new price for Virtual Server R2 Enterprise Edition - £0/$0.  See the press release here.

All that's required is registration and an agreement to allow Microsoft (ore one of its third party agents) to contact you no more than three times for feedback.

Linux machine additions are available here, additional Linux to follow.

Download Microsoft Virtual Server R2 Enterprise Edition.

Monday, April 03, 2006 10:37:21 PM (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback


Type: Error
Source: Windows SharePoint Services 2.0
Category: None
Event ID: 1000
#50070: Unable to connect to the database STS_Config on <server_name>\SharePoint. Check the database connection information and make sure that the database server is running.


This issue may occur when the SharePoint Timer Service tries to contact the configuration database when the computer starts or shuts down. By default, the configuration database in Windows SharePoint Services is named STS_config.


The error message that is mentioned in the "Symptoms" section does not affect the functionality of Windows SharePoint Services or of Windows Small Business Server 2003. If you can connect to the Windows SharePoint Services Web site successfully, you can safely ignore this error message.


To work around this issue, add the DependOnService registry entry to the following registry subkey on the server, and then set the DependOnService registry entry to MSSQL$SHAREPOINT:

Key:    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer
Type:  String
Name: DependOnService



Monday, April 03, 2006 1:30:43 PM (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Sunday, April 02, 2006

To allow large attachments to be uploaded add change of override the MaxRequestLength parameter in Machine.config or Web.config.  For instance I added the following value to Web.config to allow uploads of up to 8MB:

<httpRuntime maxRequestLength="8192" />

So the full line read:

<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" />

See http://support.microsoft.com/default.aspx?scid=kb;en-us;Q295626

Sunday, April 02, 2006 2:39:37 PM (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback


Dell lists this (and other Event IDs) as normal and to be ignored! See ImpInf0.pdf (4.88 MB).

sbs | win
Sunday, April 02, 2006 2:32:49 PM (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Saturday, April 01, 2006

827603 Remote users cannot see a Windows Small Business Server 2003
computer in My Network Places

isa | sbs
Saturday, April 01, 2006 2:47:44 AM (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback