[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] October 2011 - Posts - THE OFFICIAL BLOG OF THE SBS DIVA

October 2011 - Posts

http://msmvps.com/blogs/bradley/archive/2011/04/16/promise-me-you-won-t-try-to-do-this.aspx

I'm reblogging this as I can't find it myself under my Susan's rules of filing.

So I'll blog these key words.

SBSdiva (that hits this blog) .net 1.1 SBS 2011 don't

There.  That should let me find the blog post better.

Bottom line if you have an application that wants to install .net 1.1 (older versions of Quickbooks) it will mangle the IIS web sites on the box.

So don't install a .net 1.1 app on your server.

 

========

So your client has Quickbooks 2007 and you are migrating them to SBS 2011. First off I'm going to say you probably want to sit them down and talk about that Quickbooks 2007 multiuser version and ask them to strongly consider upgrading. For one the program/version is no longer supported. Certainly if they had employees they'd have migrated to a newer version before this if they used the payroll module. But there's another reason... you strongly do not want to be dealing with an app that wants .NET running on a SBS 2011.

When you install .net 1.1 on your SBS 2011 certain things go boom:

Companyweb

WSUS isn't WSUSing like it should.

And when I went poking around certain things just are not happy.

If your clients absolutely put their foot down -- or more likely than not someone's gone and done it and you are stuck cleaning up the mess, here's what I did to get it working --

So here's what I did to get IIS for Companyweb and WSUS working again without reinstalling the server...

From : http://forums.iis.net/p/1162661/1924871.aspx
.NET 1.1 may have agressively taken over part of IIS. Try running aspnet_regiis /i from the command prompt for the v2.0 folder. (c:\windows\microsoft.net\framework\v2.0.50727). That will register asp.net 2.0 but won't mess up 1.1. This is the most likely fix.

In my case I launched a command window as an administrator and then went to the folder of c:\windows\microsoft.net\framework\2.0.50727 and typed in aspnet_regiis /i and then did the same from c:\windows\microsoft.net\framework\v4.0.30319 and typed in aspnet_regiis /i

I then did a IISreset.

I also went to the IIS console and ensured that the IIS 1 and 4 isapi filters were allowed to run

Orignally the 1.1 said disallowed. I also let the 4.0 isapi filters be allowed.

And voila -- companyweb and WSUS work.

But do me a huge favor... get them to upgrade from Quickbooks 2007... it's old, it's out of date, it's not supported, it doesn't like UAC and you really don't want it running on that server

 

So you want your server to not have the "install updates and shut down" right?

 

Change the  "Do not display 'Install Updates and Shut down' option in the shut down windows dialog box in the Computer configuation, Administrative templates, Windows components, windows update section of group policy area.

This policy setting allows you to manage whether the 'Install Updates and Shut Down' option is displayed in the Shut Down Windows dialog box.

If you enable this policy setting, 'Install Updates and Shut Down' will not appear as a choice in the Shut Down Windows dialog box, even if updates are available for installation when the user selects the Shut Down option in the Start menu.

If you disable or do not configure this policy setting, the 'Install Updates and Shut Down' option will be available in the Shut Down Windows dialog box if updates are available when the user selects the Shut Down option in the Start menu.

Because it's hard to get the SBS bpa 2011 era to update....

you first have to be flipped over to Microsoft update...

Then you have to realize that the update doesn't behave like other updates but shows up in the system tray indicating there's an update after you have opened up the console and then you have to close the bpa console to get the update to install (that nailed me).... here's an easier way.

http://download.windowsupdate.com/msdownload/update/software/updt/2011/09/wssg-kb2600333-x64-enu_b7306de26c0ff3c4c3711d7bfb4459acf6f4e820.cab

Download that.  Now click on it and it will want to extract.  Now save it

And then run the resulting extracted file on the server.

I've put the link up on the www.sbsbpa.com as well.

Posted Sun, Oct 16 2011 23:29 by bradley | with no comments
Filed under:

Home server 2003.

Update would not install automatically via MU.
Would only install manually.

Which points out the rule of updating.  If MU doesn't work, try manually downloading and running the update.  Sometimes it will work manually installing the update where it won't via MU.

[KB2567053.log]
3.844: ================================================================================
3.844: 2011/10/11 17:24:35.031 (local)
3.844: C:\WINDOWS\SoftwareDistribution\Download\5516475221d900797308a160a3c26ef7\update\update.exe (version 6.3.4.1)
3.844: Hotfix started with following command line: /si /ParentInfo:b75eb1e95870d14aa3b0e5bde2de1891
3.844: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
5.359: DoInstallation: CleanPFR failed: 0x2
5.375: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
5.375: SetProductTypes: InfProductBuildType=BuildType.WinSB
5.391: SetAltOsLoaderPath: No section uses DirId 65701; done.
5.422: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB2567053$
5.422: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
5.469: ref tag c:\windows\system32\sp4.cab does not exist
5.469: ref tag c:\windows\system32\sp3.cab does not exist
5.469: ref tag c:\windows\system32\sp2.cab does not exist
5.469: ref tag c:\windows\system32\sp1.cab does not exist
5.469: ref tag c:\windows\system32\driver.cab does not exist
5.469: ref tag c:\windows\system32\fp40ext.cab does not exist
5.469: ref tag c:\windows\system32\fp40ext1.cab does not exist
5.469: ref tag c:\windows\system32\wms4.cab does not exist
5.469: ref tag c:\windows\system32\wms41.cab does not exist
5.469: ref tag c:\windows\system32\ims.cab does not exist
5.469: ref tag c:\windows\system32\ims1.cab does not exist
5.469: ref tag c:\windows\system32\ins.cab does not exist
5.469: ref tag c:\windows\system32\ins1.cab does not exist
5.469: Starting AnalyzeComponents
5.469: AnalyzePhaseZero used 0 ticks
5.469: OEM file scan used 0 ticks
5.656: AnalyzePhaseOne: used 187 ticks
5.656: AnalyzeComponents: Hotpatch analysis disabled; skipping.
5.656: AnalyzeComponents: Hotpatching is disabled.
5.656: FindFirstFile c:\windows\$hf_mig$\*.*
5.891: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
6.000: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
7.109: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
7.109: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
7.109: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
9.734: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
9.844: AnalyzeForBranching used 31 ticks.
9.859: AnalyzePhaseTwo used 15 ticks
9.859: AnalyzePhaseThree used 0 ticks
9.922: AnalyzePhaseFive used 63 ticks
9.922: AnalyzePhaseSix used 0 ticks
9.922: AnalyzeComponents used 4453 ticks
9.922: Downloading 2 files
9.922: bPatchMode = TRUE
9.922: Inventory complete: ReturnStatus=0, 4500 ticks
9.922: Num Ticks for invent : 4500
9.938: [dumpDownloadTask] Update.exe posting request file to download a total of 192416 bytes (192416 bytes in patches and 0 bytes in fallbacks)
9.938: dumpDownloadTask returned 0xf200 (more files to download)
10.016: KB2567053 installation did not complete.
10.016: Update.exe extended error code = 0xf200
0.516: ================================================================================
0.516: 2011/10/11 17:28:34.812 (local)
0.516: C:\WINDOWS\SoftwareDistribution\Download\5516475221d900797308a160a3c26ef7\update\update.exe (version 6.3.4.1)
0.516: Hotfix started with following command line: /si /ParentInfo:7a9e5713c11ea642912dbfd225e63b39
0.516: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.469: DoInstallation: CleanPFR failed: 0x2
1.485: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.485: SetProductTypes: InfProductBuildType=BuildType.WinSB
1.485: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.485: Express: 192,416 bytes were downloaded.
1.750: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
1.766: KB2567053 installation did not complete.
1.766: Update.exe extended error code = 0xf201
0.484: ================================================================================
0.484: 2011/10/13 13:24:14.343 (local)
0.484: C:\WINDOWS\SoftwareDistribution\Download\5516475221d900797308a160a3c26ef7\update\update.exe (version 6.3.4.1)
0.484: Hotfix started with following command line: /si /ParentInfo:10081feb80c6984d829fb1c9223d9d0d
0.484: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.437: DoInstallation: CleanPFR failed: 0x2
1.453: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.453: SetProductTypes: InfProductBuildType=BuildType.WinSB
1.469: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.469: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB2567053$
1.469: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
1.469: ref tag c:\windows\system32\sp4.cab does not exist
1.469: ref tag c:\windows\system32\sp3.cab does not exist
1.469: ref tag c:\windows\system32\sp2.cab does not exist
1.469: ref tag c:\windows\system32\sp1.cab does not exist
1.469: ref tag c:\windows\system32\driver.cab does not exist
1.469: ref tag c:\windows\system32\fp40ext.cab does not exist
1.469: ref tag c:\windows\system32\fp40ext1.cab does not exist
1.469: ref tag c:\windows\system32\wms4.cab does not exist
1.469: ref tag c:\windows\system32\wms41.cab does not exist
1.469: ref tag c:\windows\system32\ims.cab does not exist
1.469: ref tag c:\windows\system32\ims1.cab does not exist
1.469: ref tag c:\windows\system32\ins.cab does not exist
1.469: ref tag c:\windows\system32\ins1.cab does not exist
1.469: Starting AnalyzeComponents
1.469: AnalyzePhaseZero used 0 ticks
1.469: OEM file scan used 0 ticks
1.750: AnalyzePhaseOne: used 281 ticks
1.750: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.750: AnalyzeComponents: Hotpatching is disabled.
1.750: FindFirstFile c:\windows\$hf_mig$\*.*
1.750: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.750: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.765: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.765: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.765: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.797: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.812: AnalyzeForBranching used 15 ticks.
1.812: AnalyzePhaseTwo used 0 ticks
1.812: AnalyzePhaseThree used 0 ticks
1.828: AnalyzePhaseFive used 16 ticks
1.828: AnalyzePhaseSix used 0 ticks
1.828: AnalyzeComponents used 359 ticks
1.828: Downloading 2 files
1.828: bPatchMode = TRUE
1.828: Inventory complete: ReturnStatus=0, 359 ticks
1.828: Num Ticks for invent : 359
1.844: [dumpDownloadTask] Update.exe posting request file to download a total of 192416 bytes (192416 bytes in patches and 0 bytes in fallbacks)
1.844: dumpDownloadTask returned 0xf200 (more files to download)
1.922: KB2567053 installation did not complete.
1.922: Update.exe extended error code = 0xf200
0.469: ================================================================================
0.469: 2011/10/13 13:24:23.953 (local)
0.469: C:\WINDOWS\SoftwareDistribution\Download\5516475221d900797308a160a3c26ef7\update\update.exe (version 6.3.4.1)
0.469: Hotfix started with following command line: /si /ParentInfo:12c4d15a14cd28499f7da0e090d6867e
0.469: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.344: DoInstallation: CleanPFR failed: 0x2
1.344: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.344: SetProductTypes: InfProductBuildType=BuildType.WinSB
1.359: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.359: Express: 192,416 bytes were downloaded.
1.515: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
1.531: KB2567053 installation did not complete.
1.531: Update.exe extended error code = 0xf201
0.641: ================================================================================
0.704: 2011/10/16 22:07:57.562 (local)
0.704: C:\WINDOWS\SoftwareDistribution\Download\5516475221d900797308a160a3c26ef7\update\update.exe (version 6.3.4.1)
0.750: Hotfix started with following command line: /si /ParentInfo:9f05d57ec9c46f4c84dc88022ef4e156
0.750: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
3.110: DoInstallation: CleanPFR failed: 0x2
3.157: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
3.157: SetProductTypes: InfProductBuildType=BuildType.WinSB
3.172: SetAltOsLoaderPath: No section uses DirId 65701; done.
3.188: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB2567053$
3.188: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
3.188: ref tag c:\windows\system32\sp4.cab does not exist
3.188: ref tag c:\windows\system32\sp3.cab does not exist
3.188: ref tag c:\windows\system32\sp2.cab does not exist
3.188: ref tag c:\windows\system32\sp1.cab does not exist
3.188: ref tag c:\windows\system32\driver.cab does not exist
3.188: ref tag c:\windows\system32\fp40ext.cab does not exist
3.188: ref tag c:\windows\system32\fp40ext1.cab does not exist
3.188: ref tag c:\windows\system32\wms4.cab does not exist
3.188: ref tag c:\windows\system32\wms41.cab does not exist
3.188: ref tag c:\windows\system32\ims.cab does not exist
3.188: ref tag c:\windows\system32\ims1.cab does not exist
3.188: ref tag c:\windows\system32\ins.cab does not exist
3.188: ref tag c:\windows\system32\ins1.cab does not exist
3.188: Starting AnalyzeComponents
3.188: AnalyzePhaseZero used 0 ticks
3.188: OEM file scan used 0 ticks
6.094: AnalyzePhaseOne: used 2906 ticks
6.094: AnalyzeComponents: Hotpatch analysis disabled; skipping.
6.094: AnalyzeComponents: Hotpatching is disabled.
6.094: FindFirstFile c:\windows\$hf_mig$\*.*
6.094: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
6.094: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
6.125: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
6.125: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
6.125: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
6.188: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
6.219: AnalyzeForBranching used 31 ticks.
6.235: AnalyzePhaseTwo used 16 ticks
6.235: AnalyzePhaseThree used 0 ticks
6.250: AnalyzePhaseFive used 15 ticks
6.250: AnalyzePhaseSix used 0 ticks
6.250: AnalyzeComponents used 3062 ticks
6.250: Downloading 2 files
6.250: bPatchMode = TRUE
6.250: Inventory complete: ReturnStatus=0, 3062 ticks
6.250: Num Ticks for invent : 3062
7.688: [dumpDownloadTask] Update.exe posting request file to download a total of 192416 bytes (192416 bytes in patches and 0 bytes in fallbacks)
7.688: dumpDownloadTask returned 0xf200 (more files to download)
9.344: KB2567053 installation did not complete.
9.344: Update.exe extended error code = 0xf200
3.141: ================================================================================
3.141: 2011/10/16 22:08:43.687 (local)
3.141: C:\WINDOWS\SoftwareDistribution\Download\5516475221d900797308a160a3c26ef7\update\update.exe (version 6.3.4.1)
3.156: Hotfix started with following command line: /si /ParentInfo:b4b0b8f0f94760429087b292bb6a26fd
3.156: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
4.141: DoInstallation: CleanPFR failed: 0x2
4.187: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
4.234: SetProductTypes: InfProductBuildType=BuildType.WinSB
4.422: SetAltOsLoaderPath: No section uses DirId 65701; done.
4.500: Express: 192,416 bytes were downloaded.
6.453: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
6.609: KB2567053 installation did not complete.
6.609: Update.exe extended error code = 0xf201
0.578: ================================================================================
0.625: 2011/10/16 22:31:47.312 (local)
0.625: C:\WINDOWS\SoftwareDistribution\Download\5516475221d900797308a160a3c26ef7\update\update.exe (version 6.3.4.1)
0.625: Hotfix started with following command line: /si /ParentInfo:dd10f5e07253344385ca73d2f21f5042
0.625: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
0.843: DoInstallation: CleanPFR failed: 0x2
0.843: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
0.843: SetProductTypes: InfProductBuildType=BuildType.WinSB
0.843: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.859: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB2567053$
0.859: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
0.859: ref tag c:\windows\system32\sp4.cab does not exist
0.859: ref tag c:\windows\system32\sp3.cab does not exist
0.859: ref tag c:\windows\system32\sp2.cab does not exist
0.859: ref tag c:\windows\system32\sp1.cab does not exist
0.859: ref tag c:\windows\system32\driver.cab does not exist
0.859: ref tag c:\windows\system32\fp40ext.cab does not exist
0.859: ref tag c:\windows\system32\fp40ext1.cab does not exist
0.859: ref tag c:\windows\system32\wms4.cab does not exist
0.859: ref tag c:\windows\system32\wms41.cab does not exist
0.859: ref tag c:\windows\system32\ims.cab does not exist
0.859: ref tag c:\windows\system32\ims1.cab does not exist
0.859: ref tag c:\windows\system32\ins.cab does not exist
0.859: ref tag c:\windows\system32\ins1.cab does not exist
0.859: Starting AnalyzeComponents
0.859: AnalyzePhaseZero used 0 ticks
0.859: OEM file scan used 0 ticks
2.203: AnalyzePhaseOne: used 1344 ticks
2.203: AnalyzeComponents: Hotpatch analysis disabled; skipping.
2.203: AnalyzeComponents: Hotpatching is disabled.
2.203: FindFirstFile c:\windows\$hf_mig$\*.*
2.203: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
2.203: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
2.234: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
2.234: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
2.234: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
2.296: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
2.328: AnalyzeForBranching used 32 ticks.
2.343: AnalyzePhaseTwo used 15 ticks
2.343: AnalyzePhaseThree used 0 ticks
2.359: AnalyzePhaseFive used 16 ticks
2.359: AnalyzePhaseSix used 0 ticks
2.359: AnalyzeComponents used 1500 ticks
2.359: Downloading 2 files
2.359: bPatchMode = TRUE
2.359: Inventory complete: ReturnStatus=0, 1500 ticks
2.359: Num Ticks for invent : 1516
2.687: [dumpDownloadTask] Update.exe posting request file to download a total of 192416 bytes (192416 bytes in patches and 0 bytes in fallbacks)
2.687: dumpDownloadTask returned 0xf200 (more files to download)
2.781: KB2567053 installation did not complete.
2.781: Update.exe extended error code = 0xf200
0.625: ================================================================================
0.625: 2011/10/16 22:31:56.109 (local)
0.625: C:\WINDOWS\SoftwareDistribution\Download\5516475221d900797308a160a3c26ef7\update\update.exe (version 6.3.4.1)
0.625: Hotfix started with following command line: /si /ParentInfo:0ff715cbd39dc548a1da6f83aa42ee5b
0.625: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.141: DoInstallation: CleanPFR failed: 0x2
1.157: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.157: SetProductTypes: InfProductBuildType=BuildType.WinSB
1.157: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.172: Express: 192,416 bytes were downloaded.
1.516: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
1.532: KB2567053 installation did not complete.
1.532: Update.exe extended error code = 0xf201
0.594: ================================================================================
0.594: 2011/10/16 22:34:02.453 (local)
0.594: d:\1d47f189640ca6caf67652a04c6d\update\update.exe (version 6.3.4.1)
0.594: Hotfix started with following command line:
0.594: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.047: In Function TestVolatileFlag, line 12013, RegOpenKeyEx failed with error 0x2
1.047: In Function TestVolatileFlag, line 12045, RegOpenKeyEx failed with error 0x2
1.047: DoInstallation: CleanPFR failed: 0x2
1.047: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.047: SetProductTypes: InfProductBuildType=BuildType.WinSB
1.063: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.063: DoInstallation: FetchSourceURL for d:\1d47f189640ca6caf67652a04c6d\update\update_SP2GDR.inf failed
1.063: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
1.063: BuildCabinetManifest: update.url absent
1.063: Starting AnalyzeComponents
1.063: AnalyzePhaseZero used 0 ticks
1.063: OEM file scan used 0 ticks
1.329: AnalyzePhaseOne: used 266 ticks
1.329: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.329: AnalyzeComponents: Hotpatching is disabled.
1.329: FindFirstFile c:\windows\$hf_mig$\*.*
1.329: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.329: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.360: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.360: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.360: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.422: KB2567053 Setup encountered an error:  The  update.ver file is not correct.
1.454: AnalyzeForBranching used 16 ticks.
1.469: AnalyzePhaseTwo used 15 ticks
1.469: AnalyzePhaseThree used 0 ticks
1.469: AnalyzePhaseFive used 0 ticks
1.469: AnalyzePhaseSix used 0 ticks
5.188: AnalyzeComponents used 4125 ticks
5.188: Downloading 0 files
5.188: bPatchMode = FALSE
5.188: Inventory complete: ReturnStatus=0, 4125 ticks
5.875: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB2567053$
5.875: Num Ticks for invent : 4812
5.954: VerifyTargetFileSize: Unable to verify size as Source = NULL for file c:\windows\inf\HFXF.tmp
5.969: Copied file:  c:\windows\inf\branches.inf
18.813: Allocation size of drive C: is 4096 bytes, free space = 10889461760 bytes
18.829: AnalyzeDiskUsage:  Skipping EstimateDiskUsageForUninstall.
18.829: Drive C: free 10385MB req: 20MB w/uninstall: NOT CALCULATED.
18.829: CabinetBuild complete
18.829: Num Ticks for Cabinet build : 12954
18.829: DynamicStrings section not defined or empty.
18.829: FileInUse:: Detection disabled.
19.829: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
20.032: Num Ticks for Backup : 1203
20.235: Num Ticks for creating uninst inf : 203
20.250: Registering Uninstall Program for -> KB2567053, KB2567053 , 0x0
20.250: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
20.500: PFE2: Not avoiding Per File Exceptions.
20.985: GetCatVersion:  Failed to retrieve version information from C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB2567053.cat with error 0x57
21.063: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\update\update_SP2QFE.inf -> c:\windows\$hf_mig$\KB2567053\update\update_SP2QFE.inf.
21.063: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\spuninst.exe -> c:\windows\$hf_mig$\KB2567053\spuninst.exe.
21.063: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\spmsg.dll -> c:\windows\$hf_mig$\KB2567053\spmsg.dll.
21.094: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\update\spcustom.dll -> c:\windows\$hf_mig$\KB2567053\update\spcustom.dll.
21.094: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\update\KB2567053.CAT -> c:\windows\$hf_mig$\KB2567053\update\KB2567053.CAT.
21.094: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\update\update.exe -> c:\windows\$hf_mig$\KB2567053\update\update.exe.
21.094: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\update\updspapi.dll -> c:\windows\$hf_mig$\KB2567053\update\updspapi.dll.
21.110: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\update\update.ver -> c:\windows\$hf_mig$\KB2567053\update\update.ver.
21.110: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\update\updatebr.inf -> c:\windows\$hf_mig$\KB2567053\update\updatebr.inf.
21.110: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\update\eula.txt -> c:\windows\$hf_mig$\KB2567053\update\eula.txt.
21.172: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied d:\1d47f189640ca6caf67652a04c6d\update\branches.inf -> c:\windows\$hf_mig$\KB2567053\update\branches.inf.
21.329: Copied file:  C:\WINDOWS\system32\win32k.sys
22.563: Copied file (delayed):  C:\WINDOWS\system32\SET10.tmp
22.563: Copied file:  C:\WINDOWS\system32\DllCache\win32k.sys
22.657: Copied file:  c:\windows\$hf_mig$\KB2567053\SP2QFE\win32k.sys
23.891: DoInstallation: Installing assemblies with source root path: d:\1d47f189640ca6caf67652a04c6d\
23.891: Num Ticks for Copying files : 3656
23.907: Num Ticks for Reg update and deleting 0 size files : 16    
23.938: ---- Old Information In The Registry ------
23.954: Source:C:\WINDOWS\system32\SET10.tmp (5.2.3790.4905)
23.954: Destination:C:\WINDOWS\system32\win32k.sys (5.2.3790.4872)
23.954: ---- New Information In The Registry ------
23.954: Source:C:\WINDOWS\system32\SET10.tmp (5.2.3790.4905)
23.954: Destination:C:\WINDOWS\system32\win32k.sys (5.2.3790.4872)
41.641: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do.
41.641: IsRebootRequiredForFileQueue: At least one file operation was delayed; reboot is required.
                              If none are listed below, check above for delayed deletes.
41.641: IsRebootRequiredForFileQueue: c:\windows\system32\win32k.sys was delayed; reboot is required.
41.641: DoInstallation: A reboot is required to complete the installation of one or more files.
41.641: In Function SetVolatileFlag, line 11929, RegOpenKeyEx failed with error 0x2
41.641: In Function SetVolatileFlag, line 11946, RegOpenKeyEx failed with error 0x2
41.641: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
46.969: RebootNecessary = 1,WizardInput = 0 , DontReboot = 1, ForceRestart = 0

Posted Sun, Oct 16 2011 22:41 by bradley | with no comments
Filed under:

It's October... and where is there a Dell OEM build of SBS Essentials?

http://configure.us.dell.com/Dellstore/config.aspx?c=us&ccc=true&cs=04&dm=true&l=en&oc=BESW5T2&prod=false&vw=classic&fb=1

Don't get me wrong, I'm an HP gal myself, as I prefer HP's hardware over Dell,  but on an overall business view standpoint it starting to concern me that there still is not an OEM version of SBS essentials from Dell.  They are missing in action.

So for now want an OEM version of SBS Essentials?  Go with HP.

Posted Fri, Oct 14 2011 23:15 by bradley | 7 comment(s)
Filed under:

I have a client who might have had a security breach.  They noticed some very odd use accounts that no one thinks was created by anyone in their employ.  The accounts had domain admin and remote desktop rights on the server.  I think I once heard the Microsoft had free support for situations of this nature, similar to the server down support we get from them as Microsoft partners.  

Do they have support for this type of thing?

What would you do if this was a client of yours?

-------

Yes Microsoft has a free service.  Call Microsoft at 1-800-Microsoft and ask for CSS Security.  State that you need a Windows Online Forensic Analysis or WOLF  It's a tool that is installed on the server and takes a look at the event logs, a time line of events and other issues it may find.

I would also make a backup of the server and ask Microsoft to help determine when this intrusion occurred because you need to make the hard decision of what you are going to do after they help you  understand what happened.

But first thing I'd do?  Take a full backup of the server and plan on keeping that intact for investigation.  Second thing, call Microsoft.

Posted Thu, Oct 13 2011 22:26 by bradley | with no comments
Filed under:

The identity of the remote computer cannot be verified:
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/0525399b-c95f-47b2-84c8-df021d6cd949

You've all seen it since SBS 2003 era.

The very first time you connect to a RWW/RWA session you get this annoying yellow warning.  And for the bulk of us we just instruct the client to accept the cert and ignore it the next time.

But maybe you'd like to understand what it's doing and better yet how to get rid of it? 

http://weblogs.asp.net/owscott/archive/2006/11/10/Vista_2700_s-Remote-Desktop-Prompt.aspx
http://blogs.technet.com/b/askperf/archive/2008/09/23/unknown-publisher-where-did-this-dialog-box-come-from.aspx
http://blogs.technet.com/askperf/archive/2008/10/31/unknown-publisher-part-two.aspx

It's not quite as simple as you'd think because of the fact that the way RWW works is with a web based rdp connection.  On SBS 2011 the rdp file on the server is cert signed but the rdp file you reach though and get to on the workstation is not.  You will have to do a rdp cert signing on the workstation to get this to work.... or... tell your users the very first time they connect there will be this yellow box and they need to click the box to ignore it the next time.

That's probably going to be a lot faster than trying to get rdp certs deployed in a sbs network.

Hat tip to http://social.technet.microsoft.com/profile/mohitkapoor/ for that info.

But bottom line that very first yellow warning in your first rdp connection is normal and expected in the RDP 6.0 and later era.

Posted Thu, Oct 13 2011 20:26 by bradley | with no comments
Filed under:

A comment was made on the backup drive wiki that I wanted to bubble up:

As I understand it, the new backup in SBS2008 and SBS2011 will not and cannot use a drive larger than 2TB due to the technology being used to maintain the backup replica drive. As the table is structured, the size of the drive is only occasionally mentioned -- there seems to be more interest in USB 2 vs 3 interfaces. I can confirm that a 3TB Seagate drive is completely unusable for SBS2011 backup regardless of how it is formatted or partitioned. The 2TB hard disk/VHS size appears to be a real hard limit and should be better documented.
As we are starting to build these terrabyte beasts keep in mind that there's a hard limit in Windows backup that cannot backup drives larger than 2T.  Be careful building these beasts.  You may not be able to back it up with the native Windows backup.
Posted Wed, Oct 12 2011 22:28 by bradley | 6 comment(s)
Filed under:

Please now see http://msmvps.com/blogs/bradley/archive/2012/03/08/quickbooks-2012-on-sbs-2003-revisited.aspx

http://support5.quickbooks.intuit.com/support/Articles/INF16393

The system requirements for Quickbooks 2012 installs .net 4 - additional software: 250 MB for Microsoft .NET 4.0 Runtime, provided on the QuickBooks CD.  Due to this you need to be aware that while it won't mind at all being installed on SBS 2011 (standard or essentials), it will barf big time on SBS 2003 -- see - http://blog.chrisara.com.au/2008/08/net-framework-35-sp1-issue-with-windows.html

Quickbooks 2011 also won't mind SBS 2011 era servers.  Start going back too far where Quickbooks installs .net 1.1 on the Server 2008 r2 platform and you'll see issues.

So if you are rolling out Quickbooks 2012 anywhere, be aware that it would not be wise to be installing it on SBS 2003.

The SRD blog always has a risk of not patching blog post.

Here's my take on the risk of patching -- see my comments in red.

http://blogs.technet.com/b/srd/archive/2011/10/11/assessing-the-risk-of-the-october-2011-security-updates.aspx

Keep this KB - http://support.microsoft.com/kb/923100 and this http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx at hand.

Since you don't surf at your server -- is there really a risk of not patching silverlight (which probably isn't even installed on your computer)?

Today we released eight security bulletins. Two have a maximum severity rating of Critical with the other six having a maximum severity rating of Important. We hope that the table below helps you prioritize the deployment of the updates appropriately for your environment.

Bulletin

Most likely attack vector

Max Bulletin Severity

Max Exploit-ability

Likely first 30 days impact

Platform mitigations and key notes

MS11-081
(Internet Explorer)

Victim browses to a malicious website.

Critical

1

Likely to see reliable exploits developed in the next 30 days.

SEB:    The one gotcha that may bite you is this one: Some drop-down lists and combo boxes do not appear in Internet Explorer 7 after you install security update 2586448:
http://support.microsoft.com/kb/2628724  and the ‘fix’ is to upgrade to IE8.  Nice.  Not.

MS11-078
(Silverlight, .NET framework)

Victim browses to a malicious webpage with Silverlight-enabled browser.

Critical

1

Likely to see reliable exploits for Silverlight 3 in next 30 days.

Underlying issue present in .NET Framework and later versions of Silverlight (4+) but more difficult to exploit for code execution.  SEB:  Oh CRAP – this is finally a .net that I’ll want on workstations.  And CRAP again, it’s updating from 1  to 2 to 3.5 to 4.  1 to 3.5 may need an Aaron Stebner rip out tool treatment, .net 4 typically just needs a repair install done inside the program and features panel.  But on a typical XP or Win7 attached to a SBSe or 2011 you will have .net updates coming out of yoru eyeballs.  And you’ll see a Silverlight patch as well.  I have one 3.5 and one .net 4 on a win7.

MS11-077
(Win32k.sys)

Attacker logged-in to a machine locally exploits vulnerability to elevate to a higher privilege level.

Important

1

Likely to see an exploit developed for local elevation of privilege in next 30 days.

 

MS11-080
(AFD.sys)

Attacker logged-in to a machine locally exploits vulnerability to elevate to a higher privilege level.

Important

1

Likely to see an exploit developed for local elevation of privilege in next 30 days.

Vista and later platforms not affected due to IO manager hardening.

MS11-075
(DLL Preloading)

Victim browses to a malicious WebDAV share and launches an application by double-clicking a content file hosted on the attacker-controlled WebDAV share.

Important

1

Likely to see reliable exploits developed in the next 30 days.

SEB:  Yes Virginia we’re still digging out dll preloading stuff.

MS11-076
(DLL Preloading)

Victim browses to a malicious WebDAV share and launches an application by double-clicking a content file hosted on the attacker-controlled WebDAV share.

Important

1

Likely to see reliable exploits developed in the next 30 days.

SEB:  Yes Virginia we’re still digging out dll preloading stuff.

MS11-079
(Forefront Unified Access Gateway [UAG])

Attackers sends malicious XSS link to a Forefront UAG administrator. Admin clicks link which takes action on the UAG portal in the admin’s context.

Important

1

Likely to see exploit for information disclosure released in next 30 days.

SEB:  Don’t have it here, ignore this update.

MS11-082
(Host Integration Server)

Attacker sends malicious stream of network packets to Host Integration Service causing a denial of service.

Important

3

Any exploit developed could only be used for denial of service.

SEB:  Don’t have it here, ignore this update.

- Jonathan Ness, MSRC Engineering

Don’t forget iTunes update released which has security updates as well.

 

>>>Knowledge Sharing---Workaround for issue "The customized folder names might not be copied when you enable the Folder Redirection feature in Windows Vista SP1, Windows Vista SP2, and in Windows 7"<<<:
http://social.microsoft.com/Forums/en-US/partnerwinclient7rc/thread/9f004be9-a736-492a-bdcd-c3d77473198a

As KB979579 descripted, because of the customized folder settings are stored in the Desktop.ini file. When the file that uses a name that is alphabetically earlier than Desktop.ini exists in the folder and a Desktop.ini file does not yet exist on the shared drive, a new Desktop.ini file without the localized settings is created on the server when the files are redirected.

So once we encountered the same issue above, we can follow these steps as a workaround of it:

1. Set READ ONLY flag on folders in the All Users' profile on the local machine, so that the desktop.ini files are read to enable localization to work correctly.

1.1.Run commandcmd to open command prompt window.

1.2.Run these commands:

· attrib +r "C:\ProgramData\Microsoft\Windows\Start Menu\Programs"

· attrib +r "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories"

2. Copy default user desktop.ini files to the user’s profile.

2.1.Copy all files from folderC:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Accessories to folder%APPDATA%\Microsoft\Windows\Start Menu\Programs\Accessories.

2.2.Copy all files from folderC:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Accessories\Accessibility to folder%APPDATA%\Microsoft\Windows\Start Menu\Programs\Accessories\Accessibility.

2.3.Copy all files from folderC:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools to folder%APPDATA%\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools.

For more information about this topic, you can refer to this article:

The customized folder names might not be copied when you enable the Folder Redirection feature in Windows Vista SP1, Windows Vista SP2, and in Windows 7

http://support.microsoft.com/default.aspx?scid=kb;EN-US;979579


 

 

Best regards,

Alex Yu
Partner Online Technical Community
-----------------------------------------------------------------------------------------
We hope you get value from our new forums platform! Tell us what you think:
http://social.microsoft.com/Forums/en-US/partnerfdbk/threads
------------------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

Posted Tue, Oct 11 2011 0:38 by bradley | with no comments
Filed under:

>>> Sharing KB collections and build numbers of WSS 3.0 and MOSS 2007 <<<:
http://social.microsoft.com/Forums/en-US/partnerofficesharepoint/thread/e678832e-79af-4a35-8c52-b8606f132d86

Continue with the last post. Here is a summary of the Updates of Windows SharePoint Services 3.0 and Office SharePoint Server 2007, including the related KB articles and the Build Number. You can find your build version via Central Admin->Operations->Servers in Farm. The build numbers in the control panel are different.

Name

WSS KB

MOSS KB

Build #

August 2011 CU

KB2553022

KB2553020

12.0.6565.5000

June 2011 CU

KB2544399

KB2544398

12.0.6562.5000

April 2011 CU

KB 2512783

KB 2512782

12.0.6557.5000

February 2011 CU

KB2475886

KB2475885

12.0.6554.5000

December 10 CU

KB2458606

KB2458605

12.0.6550.5002-WSS, 12.0.6550.5000-MOSS

October 10 CU

KB2412268

KB2412267

12.0.0.6548

August 10 CU

KB2276474

KB2276472

12.0.0.6545

June 10 CU

KB983311

KB983310

12.0.0.6539

April 10 CU

KB981043

KB981042

12.0.0.6535

Feb 10 CU

KB 978396

KB 978395

12.0.0.6529

December 09 CU

KB 977027

KB 977026

12.0.0.6524

Oct 09 CU

KB 974989

KB 974988

12.0.0.6520

Aug 09 CU

KB 973400

KB 973399

12.0.0.6514

June 09 CU

KB 971538

KB 971537

12.0.0.6510

April 09 CU

KB 968850

KB 968851

12.0.0.6504

SP2

KB 953338

KB 953334

12.0.0.6421

Note: Service Pack 1 for Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 retired on July 13, 2010. You must upgrade to Service Pack 2, which is a requirement for the August 2010 Cumulative Update.

References:

Updates Resource Center for SharePoint Products and Technologies

http://technet.microsoft.com/en-us/office/sharepointserver/bb735839

Best regards,

Daizy Shen

Partner Online Technical Community
-----------------------------------------------------------------------------------------
We hope you get value from our new forums platform! Tell us what you think:
http://social.microsoft.com/Forums/en-US/partnerfdbk/threads
------------------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

Posted Tue, Oct 11 2011 0:36 by bradley | with no comments
Filed under:

>>>Sharing KB collections and build numbers of Sharepoint 2010 Updates<<<:
http://social.microsoft.com/Forums/en-US/partnerofficesharepoint/thread/e67bf537-f199-4a27-a275-580f4761cceb

Here is a summary of the Updates of Sharepoint 2010 products, including the related KB articles and the Build Number. Each KB has a hyperlink. You can click on the KB name and visit the corresponding KB article for detailed information. You can find your build version via Central Admin->System settings->Servers in Farm or in the Control Panel->Programs and Features.

KB collection and Build Numbers for Sharepoint 2010 Products:

Name

Sharepoint Server 2010

Sharepoint Foundation 2010

Build #

August 2011 CU

KB2553048

KB2553050

14.0.6109.5002

June 2011 CU

KB2536599

KB2536591

14.0.6106.5002

Service Pack 1

KB2460045

KB2460058

14.0.6029.1000

April 2011 CU

KB 2512800

KB 2512804

14.0.5138.5001

February 2011 CU

KB2475878

KB2475880

14.0.5136.5002

December 2010 CU

KB2459257

KB2459125

14.0000.5130.5002

October 2010 CU

KB2394320

KB2394323

14.0.5128.5000

August 2010 CU

KB2352342

KB2352346

14.0.5123.5000

June 2010 CU

KB 983497

KB 2124512

KB 2182938

KB 2204024

KB 2281364

KB 2028568

14.0.5114.5003

RTM

14.0.4762.1000(central admin)

14.0.4763.1000(control panel)

References:

Updates for SharePoint 2010 Products

http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx

Best regards,

Daizy Shen

Partner Online Technical Community
-----------------------------------------------------------------------------------------
We hope you get value from our new forums platform! Tell us what you think:
http://social.microsoft.com/Forums/en-US/partnerfdbk/threads
------------------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

 

Posted Tue, Oct 11 2011 0:34 by bradley | with no comments
Filed under:

>>>Solution Sharing----Active Directory-----August<<<:
http://social.microsoft.com/Forums/en-US/partnerwinserver/thread/17929408-5c1a-4241-904b-f0a1ff4c5b78

Post: < Removal of Orphaned Domain from production forest >
http://social.microsoft.com/Forums/en-US/partnerwinserver/thread/fc13fae8-02ae-4ba1-8ecb-f159eddf0199

Description
===============
Partner wants to know how to remove orphaned domain data from forest

Solution
===============
1. Cleaned up server metadata for the failed domain controller using the NTDSUTIL command from a server on the root domain:http://technet.microsoft.com/en-us/library/cc736378(WS.10).aspx
2. Waited for replication to occur throughout the forest.
3. Remove the DNS replication NC as per: http://support.microsoft.com/kb/887424/en-us
4. Waited for replication to occur throughout the forest.
5. Removed the orphaned domain from the forest as per: http://support.microsoft.com/kb/230306/en-us
6. Waited for replication to occur throughout the forest.
7. Apply KB 2413670 to remove the (if necessary)

*******************************************************************************************

Post: < Policy to hide "Foder options" from Control Panel (and Explorer) >
http://social.microsoft.com/Forums/en-US/partnerwinserver7rcthreads/thread/e3da59d1-5830-4b40-bdb4-7ff1dae16465

Description
===============
How to hide "Folder Options" from Control Panel

Solution
===============
Enable this policy: User Configuration\Administrative Templates\Windows Components\Windows Explorer\Removes the Folder Options menu from the Tools Menu

*******************************************************************************************

Post: < CA migration 2003(SBS)->2008R2 >
http://social.microsoft.com/Forums/en-US/partnerwinserver7rcthreads/thread/23ec7041-7d57-455d-98a8-223c96be160a

Description
===============
After migrated CA from server 2003 to server 2008 R2, partner noticed that smart card cannot be authenticated with error "Insufficient space on the card".

Cause
===============
In windows 2003 the system, the key length is 1024, however, in Windows 2008 R2, the default key length is 2048. This causes "insufficient space" issue.

Solution
===============
Create a copy of the smartcard logon template, and then select key size.

More Information
===============
http://blogs.technet.com/b/configmgrteam/archive/2009/04/29/resolving-certreq-errors-key-size-and-user-permissions.aspx


 

 

Best regards,

Alex Yu
Partner Online Technical Community
-----------------------------------------------------------------------------------------
We hope you get value from our new forums platform! Tell us what you think:
http://social.microsoft.com/Forums/en-US/partnerfdbk/threads
------------------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

Posted Tue, Oct 11 2011 0:27 by bradley | with no comments
Filed under:

>>>Knowledge Sharing--Publish Direct IP prienters in AD without an printing server<<<:
http://social.microsoft.com/Forums/en-US/partnerwinserver/thread/7dfec84a-4bad-44ef-bf80-e965b8756740

Sometimes, due to policy factors or other considerations, we need publish direct IP printing for a large number of printers instead of using print servers to manage the printers.

As we know, to publish printers in AD, a Print Queue needs to be shared that it can be published in AD. It does not matter if this Print Queue is hosted on a Client or a Print Server. This means we can publish direct IP printers in AD without any printing server. To do so, we can use script pubprn.vbs.

The following is the output of commandcscript C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US\pubprn.vbs -?, it will help us getting start with this VBS script:

C:\>cscript C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US\pubprn.vbs -?

Microsoft (R) Windows Script Host Version 5.8

Copyright (C) Microsoft Corporation. All rights reserved.

Usage: [cscript] pubprn.vbs server "LDAP://OU=..,DC=..."

server is a Windows server name (e.g.: Server) or UNC printer name (\\Server\Printer)

"LDAP://CN=...,DC=..." is the DS path of the target container

Example 1: pubprn.vbs MyServer "LDAP://CN=MyContainer,DC=MyDomain,DC=Company,DC=Com"

Example 2: pubprn.vbs \\MyServer\Printer "LDAP://CN=MyContainer,DC=MyDomain,DC=Company,DC=Com"

For more information, we can refer to this article:

Pubprn.vbs

http://technet.microsoft.com/en-us/library/cc753116(WS.10).aspx

The following article also descripts the differences of using print servers vs. direct printing:

http://download.microsoft.com/download/6/6/a/66ab0a8f-8418-47bc-9c4f-b2c341ac3691/When%20to%20Use%20a%20Print%20Server.doc


 

 

Best regards,

Alex Yu
Partner Online Technical Community
-----------------------------------------------------------------------------------------
We hope you get value from our new forums platform! Tell us what you think:
http://social.microsoft.com/Forums/en-US/partnerfdbk/threads
------------------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

Posted Tue, Oct 11 2011 0:26 by bradley | with no comments
Filed under:

>>>Solution Sharing----Active Directory-----August<<<:
http://social.microsoft.com/Forums/en-US/partnerwinserver7rcthreads/thread/78a138b2-dc3d-4959-9884-a960026a6d12

Post: < Event ID: 1058 >
http://social.microsoft.com/Forums/en-US/partnerwinserver7rcthreads/thread/06e74db4-5021-40df-9892-3e9ab272dc17

Description
===============
one client got error 1058 every five minutes with message "The processing of Group Policy failed."

Cause
===============
Default domain policy "{31B2F340-016D-11D2-945F-00C04FB984F9}" broken.

Solution
===============
Logon one domain controller, backup Default Domain Policy, and then use command "dcgpofix /target: Domain" to fix Default Domain Policy(without quotes).

********************************************************************

Post: < Lock down Display Settings using Group Policy >
http://social.microsoft.com/Forums/en-US/partnerwinclientxp/thread/db3acf03-1a9f-4da3-b4d3-0415a322a097

Description
===============
Partner cannot see any more options other than "Windows Components" in Administrator Templates

Cause
===============
Files were lost in folder %windir%\system32\GroupPolicy\Adm

Solution
===============
Copy missing files from a working domain controller.


Best regards,

Alex Yu
Partner Online Technical Community
-----------------------------------------------------------------------------------------
We hope you get value from our new forums platform! Tell us what you think:
http://social.microsoft.com/Forums/en-US/partnerfdbk/threads
------------------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

Posted Mon, Oct 10 2011 23:50 by bradley | with no comments
Filed under:

How to join Linux server into Active Directory on SBS 2008 network — Tech Notes Desk Blog:
http://blog.technotesdesk.com/?p=603

Spotted this blog and it's good info for both SBS 2008 and SBS 2011.

Posted Sun, Oct 9 2011 23:34 by bradley | 5 comment(s)
Filed under:

Reinstalling Certificate Authority Role on SBS 2011 Essentials:
http://support.microsoft.com/kb/2581361/en-us?sd=rss&spid=1167

SBS2011: Unable to login to RWA - An error (87) occurred while enumerating the groups. The group's SID could not be resolved:
http://support.microsoft.com/kb/2585635/en-us?sd=rss&spid=1167

Posted Sat, Oct 8 2011 23:52 by bradley | with no comments
Filed under:

http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/88b35db7-43cf-4162-8d18-831b09d98f3b/

If you are having issues getting your SBS 2011 era bpa up to the 1.1 version here are some things that -should- work.  Let me know if it still doesn't get you to an updated bpa.

If you have NOT flipped the server over to Microsoft update from Windows update it won't detect the bpa update.

==============
Notes from Les' case.

It looks like there are a couple of solutions here.
Once you have the BPA installed and you run it - you'll notice that the
Microsoft Baseline Configuration Analyzer is at Version 2, and you'll see a
drop down box containing Windows Server Solutions Best Practices Analyzer -
select that and 'start scan'.
If the WSSBPA is at Version 1.0 - you need an update. If you see an icon in
the notification area for the update, install it and you are golden.
If you are at Version 1.0 and you are *not* notified of an update, you'll
have to take some action.
1. Opt in to Microsoft Update
On the SBS 2011 Server, Start | All Programs | Windows Update. Click on
"receive updates for Windows and other products" to opt in to Microsoft
Update.
Scan for new updates, wait for the scan to complete. You don't need to
install any found updates, you can close the update window.
Start the BPA, and wait a few seconds and you should see the update icon in
the notification area.
2. At your own risk
Looking at logfiles, it seems the update comes from here:
If you're comfortable with it, download and install the update.
I've tried both methods with success.
Thanks very much to those that helped behind the scenes - the BPA is an
extremely valuable tool and everyone appreciates the help in getting it
installed and updated.
--
-----------------------------------------------
Les Connor [Ex SBS MVP 2001-2011]

From the Cloud essentials newsletter comes this info:

Great News! Microsoft is waiving the requirement to sell 50 seats of each online service in your organization's first year of program enrollment because your organization enrolled in the Microsoft Cloud Essentials Pack between November 1, 2010 and June 30, 2011. This means your organization can continue using these valuable Microsoft Online Services Internal Use Rights benefits in the second year of program enrollment.


Okay that's good...but.... the last I remember reading it was a mere 50 seats of a single online service, now it's 50 seats of each?  Does that include Azure too?  Stay tuned will investigate.

 

Posted Fri, Oct 7 2011 14:59 by admin | with no comments
Filed under:
More Posts « Previous page - Next page »