Quantcast
Channel: The Official Configuration Manager Support Team Blog
Viewing all 715 articles
Browse latest View live

KB: How to sequence the Microsoft System Center Configuration Manager 2007 R3 Admin Console using Microsoft App-V

$
0
0

imageHere’s one more Knowledge Base article we published today. This one shows you how to sequence (virtualize) the ConfigMgr admin console in App-V.

=====

Symptoms

When trying to Sequence (virtualize) the System Center Configuration Manager 2007 (ConfigMgr) administrator’s console, the resulting package will generate the following error and fail to run:

MMC cannot initialize the snap-in

Resolution

Using the steps below, you can virtualize the admin console and have it run successfully.

NOTE In the example below, it is assumed that we are sequencing the Microsoft System Center Configuration Manager 2007 R3 admin console for the 64-bit version of Windows 7 Service Pack 1.

1. Follow Best Practices for the Microsoft Application Virtualization Sequencer : http://technet.microsoft.com/en-us/library/dd351420.aspx

2. Build the clean system with 64-bit version of Windows 7 SP1 and join it to the domain.

3. Install the APPV 4.6 SP1 Sequencer with Hotfix 3 (http://support.microsoft.com/kb/2571168). Launch the Microsoft Application Virtualization Sequencer and select Create New Virtual Application Package.

4. Select Create Package (Default) option and Click Next. Note that Prepare the Computer for Creating a Virtual Package may give the Warning “Windows Defender is active”. If so, launch the Services.msc snap-in and stop the Windows Defender service. After doing so, click refresh and then click Next.

5. Select the Standard Application (default) option and click Next.

6. On the Select Installer Screen, browse to “SPLASH.HTA” on the Configuration Manager (ConfigMgr) installation media and click Next.

7. Name the Package SCCMConsole.001 and leave other options as the defaults and click Next.

8. Once the ConfigMgr installation screen appears, click Install Configuration Manager 2007 SP2 and click Next.

9. Select Install or Upgrade an Administrator Console and click Next.

10. Accept license agreement and Click Next.

11. Select No, I do not want to participate right now and click Next.

12. Leave the Destination Folder to the default (i.e. C:\Program Files(x86)\Microsoft Configuration Manager Console\) and click Next.

13. Provide your site Server Name and Click Next, then Next again.

14. Ensure the Pre-check passes then click on Begin Install.

15. Once the installation finishes click Next and then click Finish.

16. Back on the Installation screen on the Sequencer, click on the “Run” option to install the ConfigMgr R3 prerequisite hotfix http://support.microsoft.com/kb/977384) and R3.

17. Provide the path to the 977384 hotfix and choose Install.

18. When complete and back at the Installation screen on the Sequencer, click on the “Run” option to install R3.

19. Click on Run and provide the path to R3’s “SPLASH.HTA” and click Next and install R3.

20. When complete, click on I am Finished installing

21. Select the ConfigMgr console and run it. After launching the console close it. Click Next to review the installation report and click Next when you’re done.

22. Select the Customize option and click Next

23. Now under Edit Short Cut screen, right Click and edit the ConfigMgr Console.

24 Click on “Change Icon…” and browse to “C:\Program Files\Microsoft Configuration Manager Console\bin\i386\” and select “SETUP.EXE”

25. Select the proper icon and provide the version No: 4.00.6487.2157

26. Click “Save”

27. Right click “ConfigMgr Documentation” and click “Edit”

28. Click on “Change Icon…” and browse to “C:\Windows” and select “hh”

29. Select the proper icon and click “Save”

30. Right click on ConfigMgr setup and select Remove.

31. Right click on ConfigMgr Setup Repair Wizard and select Remove.

32. Click next and then Run ALL.

33. Select the Target OS, click Next and then select Create the Package. The Package will be saved as SCMMConsole.001.

34. Copy the Package to the App-V management content share.

35. Edit the OSD file of ConfigMgr Console.OSD in Notepad. Change the VALUE of <SUBSYSTEM VALUE= "windows"/> to <SUBSYSTEM VALUE= "console"/> and save the OSD file.

36. Now follow the normal procedure to import the Package in to your APPV Management server and verify that the console is published to the APPV users.

When you double click ConfigMgr Console on an App-V client you may see the error “MMC cannot initialize the snap-in.” If so, hold the Shift Key and right-click on ConfigMgr Console and select Run as different user. Provide whichever user credentials that have access to the ConfigMgr site server.

More Information

This is published on the Microsoft App-V blog here:

http://blogs.technet.com/b/appv/archive/2012/03/20/how-to-sequence-the-system-center-configuration-manager-2007-r3-admin-console-with-microsoft-app-v.aspx

Also see the following Knowledge Base article:

2559075 - Elevation and Run-As Considerations in Microsoft App-V Environments (http://support.microsoft.com/kb/2559075)

=====

For the most current version of this article please see the following:

2685079 : How to sequence the Microsoft System Center Configuration Manager 2007 R3 Admin Console using Microsoft App-V

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/


New Knowledge Base articles for System Center 2012 Configuration Manager

$
0
0

imageNow that System Center 2012 Configuration Manager has released, we have some KB articles that describe a few of the things we saw during the beta that you may run into. Nothing really major, just a few tips and FYIs you may want to be aware of. If you have plans on rolling out ConfigMgr, or even if you already have, you might want to take a quick look at these just in case you happen to run across them somewhere down the road.

2679005

An App-V 4.5 package fails to run on Windows 7 or Windows Server 2008 R2 in a System Center 2012 Configuration Manager environment

2683908

App-V applications cannot be streamed from a Configuration Manager Distribution Point if the "Bypass proxy server for local addresses" option is set

2688244

Old System Center 2012 Configuration Manager application Deployment Type source content remains in the client cache after the application is removed

2679653

The lastLogonTimestamp attribute in System Center 2012 Configuration Manager may not be accurate

2681449

Descriptions are not provided for the ResultDetail values in the "v_CH_EvalResults" view in System Center 2012 Configuration Manager

2688238

The Microsoft Network Inspection service started by System Center 2012 Configuration Manager may be stopped by Active Directory Group Policy

2688239

Many warning messages for PolicyAgentInstanceProvider are logged when you install the System Center 2012 Configuration Manager client

2691080

The Ccmexec.exe service is not automatically restarted after the WMI service is paused and restarted in System Center 2012 Configuration Manager

2688287

The System Center 2012 Configuration Manager console crashes when an item in a list view is moved to a collapsed group

2691547

The "Computers with a specific virtual application" or "Computers with a specific virtual application package" reports in System Center 2012 Configuration Manager do not display data

2692920

"In Progress" status is displayed in the System Center 2012 Configuration Manager console for the installation of a mobile app that requires the removal of another, unremoval application

2691543

Deploying a non-English operating system using System Center 2012 Configuration Manager fails with Error 31: A device attached to the system is not functioning

2680765

Changes made to Video Hardware Acceleration settings in a System Center 2012 Configuration Manager Remote Control session are reverted when the session ends

2690414

Keyboard shortcuts used in a System Center 2012 Configuration Manager Remote Desktop session may be intercepted by a Remote Control viewer session

2678905

The System Center 2012 Configuration Manager client installation fails when BITS is not installed

2680249

A failure is reported if you remove a zero value from the Return Codes tab in System Center 2012 Configuration Manager

2683900

Changes to the Deployment Type in System Center 2012 Configuration Manager are deployed unexpectedly and cannot be rolled back

2688277

The System Center 2012 Configuration Manager Application Catalog fails after reinstalling the Application Catalog Web Service Point using different install options

2688285

The Apply button is unavailable after clearing the "Enable PXE support for clients" option on a System Center 2012 Configuration Manager Distribution Point

2688288

Changing the SQL Service Broker port while performing a System Center 2012 Configuration Manager site recovery causes the site to remain in Maintenance Mode

2688242

Clients are not updated with the latest definitions after installing the Endpoint Protection site role in System Center 2012 Configuration Manager

2688247

SQL Server cumulative updates must be manually installed on secondary System Center 2012 Configuration Manager sites that use SQL Server Express

2691550

Multiple error messages are logged in the System Center 2012 Configuration Manager Distmgr.log file when you update shared Distribution Points

2691875

Different results are displayed for software updates when you use saved searches in non-English versions of System Center 2012 Configuration Manager

2691946

You cannot reinstall a System Center 2012 Configuration Manager SMS Provider on a server had the same provider previously uninstalled

2693104

Migrating objects to System Center 2012 Configuration Manager fails with "Could not find the specified instance"

2693122

A System Center 2012 Configuration Manager Distribution Point contains no deployment package after using the Download Software Updates wizard

2683915

Installing a secondary System Center 2012 Configuration Manager site fails when using the default SQL instance name

2687393

A System Center 2012 Configuration Manager Windows Installer-based Deployment Type with a malformed command line fails with an MSIExec error

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Troubleshooting tip: Downloading software updates to an Update List fails with "The requested header could not be found"

$
0
0

imageHi everyone, Tyler Franke here again with another troubleshooting tip for you. When you’re in the System Center Configuration Manager 2007 administrative console and trying to download software updates to an update list, it may fail with an error stating the following:

The requested header could not be found

Furthermore, if you leverage the PatchDownloader.log you will find an entry similar to the following:

Downloading content for ContentID = 27377, FileName = windowsserver2003.windowsxp-kb2621440-x64-enu.exe. Software Updates Patch Downloader 3/22/2012 3:34:37 PM 1337928 (0x146A48)
HttpQueryInfo HTTP_QUERY_CONTENT_LENGTH failed 12150 Software Updates Patch Downloader 3/22/2012 3:34:37 PM 1335744 (0x1461C0)
Download http://download.windowsupdate.com/msdownload/update/software/secu/2012/02/windowsserver2003.windowsxp-kb2621440-x64-enu_337d75494557b29c69230ca182054ad65489847b.exe to C:\Users\SJSIMM~1\AppData\Local\Temp\2\CAB161.tmp returns 12150 Software Updates Patch Downloader 3/22/2012 3:34:37 PM 1335744 (0x1461C0)
ERROR: DownloadContentFiles() failed with hr=0x80072f76 Software Updates Patch Downloader 3/22/2012 3:34:37 PM 1337928 (0x146A48)

Cause

A content filtering device was closing the session. Notice in the Netmon frames below that the connection is initiated by the site server with IPv4 address 192.168.1.100, however the device with IPv4 address 192.168.1.200 is where the traffic is being sent first to try to actually go out and initiate the download. You’ll notice that as part of the HTTP connection initiated by the site server we have to keep the session alive (i.e. ProxyConnection: Keep-Alive) however the device with IPv4 address 192.168.1.200 essentially deconstructs the packet and then closes the connection (i.e. ProxyConnection: close) therefore ending any chances the site server had of downloading the software updates.

The items/lines that I've bolded in the Netmon frames below are the most noteworthy and demonstrate the content filtering device closing the connection.

Frame: Number = 28900, Captured Frame Length = 361, MediaType = ETHERNET
- Ethernet: Etype = Internet IP (IPv4),DestinationAddress:[06-7A-8B-9C-10-11],SourceAddress:[00-1A-2B-3C-04-05]
- DestinationAddress: BROADCOM CORPORATION BCE088 [06-7A-8B-9C-10-11]
Rsv: (000000..)
UL: (......0.) Universally Administered Address
IG: (.......0) Individual address (unicast)
+ SourceAddress: Hewlett Packard D89A3B [00-1A-2B-3C-04-05]
EthernetType: Internet IP (IPv4), 2048(0x800)
- Ipv4: Src = 192.168.1.100, Dest = 192.168.1.200, Next Protocol = TCP, Packet ID = 17864, Total IP Length = 347
+ Versions: IPv4, Internet Protocol; Header Length = 20
+ DifferentiatedServicesField: DSCP: 0, ECN: 0
TotalLength: 347 (0x15B)
Identification: 17864 (0x45C8)
+ FragmentFlags: 16384 (0x4000)
TimeToLive: 128 (0x80)
NextProtocol: TCP, 6(0x6)
Checksum: 0 (0x0)
SourceAddress: 192.168.1.100
DestinationAddress: 192.168.1.200
- Tcp: Flags=...AP..., SrcPort=50355, DstPort=HTTP Alternate(8080), PayloadLen=307, Seq=1611337238 - 1611337545, Ack=2596688289, Win=16425 (scale factor 0x2) = 65700
SrcPort: 50355
DstPort: HTTP Alternate(8080)
SequenceNumber: 1611337238 (0x600B0E16)
AcknowledgementNumber: 2596688289 (0x9AC651A1)
+ DataOffset: 80 (0x50)
+ Flags: ...AP...
Window: 16425 (scale factor 0x2) = 65700
Checksum: 0x2251, Disregarded
UrgentPointer: 0 (0x0)
TCPPayload: SourcePort = 50355, DestinationPort = 8080
-
Http: Request, GET http://download.windowsupdate.com/msdownload/update/software/secu/2012/02/windowsserver2003.windowsx
Command: GET

- URI: http://download.windowsupdate.com/msdownload/update/software/secu/2012/02/windowsserver2003.windowsxp-kb2621440-x64-enu_337d75494557b29c69230ca182054ad65489847b.exe
Location: http://download.windowsupdate.com/msdownload/update/software/secu/2012/02/windowsserver2003.windowsxp-kb2621440-x64-enu_337d75494557b29c69230ca182054ad65489847b.exe
ProtocolVersion: HTTP/1.1
Accept: */*
UserAgent: Download Progress
Host: download.windowsupdate.com
ProxyConnection: Keep-Alive
Pragma: no-cache
HeaderEnd: CRLF

Frame: Number = 28969, Captured Frame Length = 364, MediaType = ETHERNET
- Ethernet: Etype = Internet IP (IPv4),DestinationAddress:[00-1A-2B-3C-04-05],SourceAddress:[06-7A-8B-9C-10-11]
- DestinationAddress: Hewlett Packard D89A3B [00-1A-2B-3C-04-05]
Rsv: (000000..)
UL: (......0.) Universally Administered Address
IG: (.......0) Individual address (unicast)
+ SourceAddress: BROADCOM CORPORATION BCE088 [06-7A-8B-9C-10-11]
EthernetType: Internet IP (IPv4), 2048(0x800)
- Ipv4: Src = 192.168.1.200, Dest = 192.168.1.100, Next Protocol = TCP, Packet ID = 3683, Total IP Length = 350
+ Versions: IPv4, Internet Protocol; Header Length = 20
+ DifferentiatedServicesField: DSCP: 0, ECN: 0
TotalLength: 350 (0x15E)
Identification: 3683 (0xE63)
+ FragmentFlags: 16384 (0x4000)
TimeToLive: 64 (0x40)
NextProtocol: TCP, 6(0x6)
Checksum: 2612 (0xA34)
SourceAddress: 192.168.1.200
DestinationAddress: 192.168.1.100
- Tcp: Flags=...AP..., SrcPort=HTTP Alternate(8080), DstPort=50355, PayloadLen=310, Seq=2596688289 - 2596688599, Ack=1611337545, Win=54 (scale factor 0x7) = 6912
SrcPort: HTTP Alternate(8080)
DstPort: 50355
SequenceNumber: 2596688289 (0x9AC651A1)
AcknowledgementNumber: 1611337545 (0x600B0F49)
+ DataOffset: 80 (0x50)
+ Flags: ...AP...
Window: 54 (scale factor 0x7) = 6912
Checksum: 0xB4CF, Good
UrgentPointer: 0 (0x0)
TCPPayload: SourcePort = 8080, DestinationPort = 50355
- Http: Response, HTTP/1.1, Status: Ok, URL: http://download.windowsupdate.com/msdownload/update/software/secu/2012/02/windowsserver2003.windowsx
ProtocolVersion: HTTP/1.1
StatusCode: 200, Ok
Reason: OK
Date: Fri, 06 Apr 2012 18:56:46 GMT
Last-Modified: Wed, 22 Feb 2012 21:36:04 GMT
+ ContentType: application/octet-stream
ETag: "03a6bfaa9f1cc1:0"
Accept-Ranges: bytes
Server: Microsoft-IIS/7.5
XPoweredBy: ASP.NET
Age: 261162
ProxyConnection: close
Via: 1.1 localhost.localdomain
HeaderEnd: CRLF

NOTE In this particular case the device was a Websense content filtering device but any device that performs similar functions can cause the same issue.

Resolution

To fix this, you’ll need to configure the content filtering device to allow their Configuration Manager site server access to at least the following list of websites as taken from KB885819.

Quite commonly the cache of the web filtering device will also have to be cleared or purged after making the necessary changes to allow the site server access to the required web addresses. Failure to do so can leave the cache intact and not allow for a successful connection.

Websites to allow:

http://download.windowsupdate.com
http://*.download.windowsupdate.com
http://download.microsoft.com
https://*.update.microsoft.com
http://*.update.microsoft.com
https://update.microsoft.com
http://update.microsoft.com
http://*.windowsupdate.com
http://*.windowsupdate.microsoft.com
http://windowsupdate.microsoft.com
https://*.windowsupdate.microsoft.com
http://ntservicepack.microsoft.com
http://wustat.windows.com

More Information

885819 - You experience problems when you access the Windows Update Version 6 Web site through a server that is running ISA Server
(http://support.microsoft.com/default.aspx?scid=kb;EN-US;885819)

Tyler Franke | Senior Support Escalation Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Announcement: Configuration Manager Documentation Library Update for April 2012

$
0
0
The Documentation Library for System Center 2012 Configuration Manager and the Configuration Manager 2007 Documentation Library have been updated on the web and the latest content has Updated: April 1, 2012 at the top of the topic. For those of you...(read more)

After migrating Software Updates to System Center 2012 Configuration Manager, it appears not all packages were migrated

$
0
0

Question2Just a quick note on an issue you might see that can be a little bit confusing if you’re not aware of what’s going on. After migrating Software Update packages from System Center Configuration Manager 2007 to System Center 2012 Configuration Manager, it may appear that not all packages were migrated successfully. Usually the way this plays out is that after the migration, the admin looks at the updates package, sees fewer updates than he started with, and thinks something is wrong.

No cause for alarm though, as chances are all of the packages were actually migrated successfully. So why the discrepancy? Well there was an issue that I won’t get into here where ConfigMgr 2007 didn’t always display superseded updates correctly, so what’s happening is that the missing updates were removed because they were expired or superseded and no longer show up.

Hope this helps!

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

New Top Solutions feeds for System Center products

$
0
0

wrenchWe are very happy to announce that seven of the Product Solution Centers on http://support.microsoft.com are featuring new Top Solutions sections that pull dynamically from the Top Solutions RSS feeds. The Top Solutions are usually listed on the page for the Key Resources tab.

The following solution centers have dynamic Top Solutions; the rest will be updated in the near future. Check out the new look and functionality!

If you want to keep up to date on all the latest top solutions you’ll definitely want to check these out.

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Announcement: New Quizzes for System Center 2012 Configuration Manager

$
0
0
We’re pleased to announce that we’ve just published a new set of our popular quizzes for System Center 2012 Configuration Manager. These 14 quizzes are a fun way to learn about some of the capabilities of the product and also to help you to...(read more)

Fix: Unable to connect CAS or Primary to the SQL database during the System Center 2012 Configuration Manager setup

$
0
0

Toolbox3Hi everyone, Dennis Donahoe here with a couple tips on how to fix an issue you may see setting up a new install of Configuration Manager. In a new installation of System Center 2012 Configuration Manager (ConfigMgr), you may find that you cannot connect to SQL when installing with a remote SQL 2008 R2 SP1 named instance. If this happens, some of the issues that you should check are listed below. They may not all completely prevent communication with SQL but they are all base requirements or strong recommendations for proper installation and should be checked during troubleshooting.

1. Check the SQL Server Configuration Manager named instance network configuration.

a. Open SQL server 2008 Configuration Manager  in the start menu

b. Select SQL server Network Configuration

c. Select the instance the database is expected to use

d. In the right pane right click on TCP/IP and select Properties

clip_image001

If the named instance is using dynamic ports then the port shown will be blank.   Using dynamic ports is not supported in System Center 2012 Configuration Manager as it requires a fixed port.   You can manually select a port or you can check the SQL error log and see what port it is currently using and set that as the port if no other application databases are in that instance.

2. The SQL Server Service Broker must be enabled for the Configuration Manager database.

clip_image002

The image above shows the Service Broker disabled (Broker Enabled set to False).   This needs to be set to True on the ConfigMgr database only. To do this, right-click on the database and select Properties –> Options (SQL 2008 R2) or run Select * from sys.databases to see service broker status (1=enabled).

3. Microsoft recommends using a domain account for the SQL server service account. With a Domain account as a service account, we must insure that SPN's are configured for the service account for Netbiosname:port and fqdn:port. Both Netbios and FQDN must be configured.

4. Check to see if any other Configuration Manager databases are installed on this instance in SQL. Having another System Center Configuration Manager 2007 database in the same instance is not recommended and having another System Center 2012 Configuration Manager instance is unsupported.

5. Verify SQL has the correct Cumulative Update. SQL Server 2008 R2 SP1 Requires CU4.  Information for all Supported SQL versions and their required updates are contained in the links below:

How to determine the version and edition of SQL Server and its components : http://support.microsoft.com/kb/321185

Configurations for the SQL Server Site Database : http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLDBconfig

Supported Configurations for Configuration Manager : http://technet.microsoft.com/en-us/library/gg682077.aspx

Dennis Donahoe | Senior Support Escalation Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/


Troubleshooting Content Mismatch Warnings on a Distribution Point in System Center 2012 Configuration Manager

$
0
0
You might see content mismatch warnings in System Center 2012 Configuration Manager when content validation runs and determines that there is a discrepancy between the expected list of packages in WMI on the distribution point and the packages in the...(read more)

FEP 2010 antimalware definition updates are not deployed as expected via an Automatic Deployment Rule in System Center 2012 Configuration Manager

$
0
0

Toolbox3Hi everyone, Peter Gallagher here and I wanted to talk about one of the new features in System Center 2012 Configuration Manager (ConfigMgr). The feature is the ability to automatically deploy software updates to clients and it can be utilized to automatically deploy Forefront Endpoint Protection 2010 antimalware definition updates to ConfigMgr clients. For more information on deploying Forefront Endpoint Protection 2010 with Configuration Manager as well as how to create an Automatic Deployment Rule for Forefront Endpoint Protection 2010 antimalware definition updates, please see the following: http://technet.microsoft.com/en-us/library/hh508770.aspx.

The issue I wanted to talk about was one where after following http://technet.microsoft.com/en-us/library/hh508770.aspx, antimalware definition updates may not be automatically deployed to clients as expected.

When this occurs, per the UpdatesDeployment.log and WindowsUpdate.log on the client, other software updates may be deployed successfully, but examining the UpdatesDeployment.log on the client shows that the client is not detecting Forefront Endpoint Protection 2010 as a product. The only indication of an error or problem will be the status of Forefront Endpoint Protection 2010 antimalware definition updates in the Windows Security Center on the client or the Configuration Manager console.

This issue can occur if the product “Forefront Endpoint Protection 2010” is not selected on the Software Update Point Component in Configuration Manager. An Automatic Deployment Rule in System Center 2012 Configuration Manager DOES NOT verify that the corresponding products or classifications that are selected are also selected on the Software Update Point itself.

To resolve this issue perform the following:

1. On the Central Administration Server (CAS), navigate to Administration\Overview\Site Configuration\Sites.

2. In the results pane on the right, highlight the servername that has the type of “CAS”. If you have a single server install, highlight the server listed.

3. In the ribbon at the top, click Configure Site Components and in the dropdown select Software Update Point.

4. Select the Products tab and then place a check next to Forefront Endpoint Protection 2010.

5. Review the Languages/Classifications tabs to ensure that the items selected in the Automatic Deployment Rules are also selected on the properties of the Software Update Point. Click OK when complete. There is no need to manually initiate a synchronization as Configuration Manager will detect a change (step 4 above) and automatically start a synchronization.

Note that this example is specific to Forefront Endpoint Protection 2010 antimalware definition updates, however the process applies to any Automatic Deployment Rule in System Center 2012 Configuration Manager. If a product/classification is selected in an Automatic Deployment Rule, the corresponding product/classification must be selected in the Software Update Point configuration screen.

Peter Gallagher | System Center Support Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

KB: After moving the System Center 2012 Configuration Manager SQL Site Database to another drive, creating a new Software Update package or a new application fails

$
0
0

imageHere’s a new Knowledge Base article we published today. This one discusses an issue where after moving the System Center 2012 Configuration Manager SQL Site Database to another drive, creating a new Software Update group, Software Update package, or creating a new application fails.

=====

Symptoms

After moving the System Center 2012 Configuration Manager SQL Site Database to another drive, creating a new Software Update group, Software Update package, or creating a new application fails and errors similar to the following are logged in the SMSProv.log file:

*** *** Unknown SQL Error! SMS Provider 14-03-2012 07:56:47 2016 (0x07E0)
*~*~*** Unknown SQL Error! ThreadID : 2016 , DbError: 50000 , Sev: 16~*~* SMS Provider 14-03-2012 07:56:47 2016 (0x07E0)
*** [24000][0][Microsoft][SQL Server Native Client 10.0]Invalid cursor state SMS Provider 14-03-2012 07:56:48 2016 (0x07E0)
*~*~[24000][0][Microsoft][SQL Server Native Client 10.0]Invalid cursor state *** Unknown SQL Error! ThreadID : 2016 , DbError: 0 , Sev: 0~*~* SMS Provider 14-03-2012 07:56:48 2016 (0x07E0)

SQL Profiler provides the following additional details:

An error occurred in the Microsoft .NET Framework while trying to load assembly id 65539. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:

System.IO.FileLoadException: Could not load file or assembly 'cryptoutility, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)

System.IO.FileLoadException:

at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)

at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

at System.Reflection.Assembly.Load(String assemblyString)

Cause

This can occur if the SQL Site Database MDF and LDF files are moved to a different drive. For example, if originally the Configuration Manager Site Database was created on C:\Program files\MSSQL server\data but then later the MDF and LDF files were moved to different drive to save space (e.g. D:\CM2012DB), you may see the issue above.

Note that this is a supported SQL operation. For more information see the following:

How to move SQL Server databases to a new location by using Detach and Attach functions in SQL Server - http://support.microsoft.com/kb/224071

How to Move SQL Server Data File(s) (.mdf) and Log File(s) (.ldf) Files From One Location to Another - http://support.microsoft.com/kb/965095

This occurs with System Center 2012 Configuration Manager because by default, the SQL Site Database has the SQL TRUSTWORTHY property set to ON, however when you detach and reattach the database it gets set to OFF. When the database is not configured with this setting ON, <ConfigMgr_Install>\bin\x64\CryptoUtility.dll fails to load into SQL and you get an 'invalid cursor state' message.

Resolution

To resolve this issue complete the following steps:

1. Manually set the property back to ON by running the following command against your CM database:

ALTER DATABASE CM_SAG SET TRUSTWORTHY ON

2. Ensure that the database that was moved is owned by SA.

More Information

An iDNA of the SQL process shows the exception:

 

Number of exceptions of this type: 3
Exception MethodTable: 000007fef2524e30
Exception object: 0000000201027798
Exception type: System.IO.FileLoadException
Message: Could not load file or assembly 'cryptoutility, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)
InnerException: <none>
StackTrace (generated):
SP IP Function
00000000204F8DC0 0000000000000001 System.Reflection.Assembly._nLoad(System.Reflection.AssemblyName, System.String, System.Security.Policy.Evidence, System.Reflection.Assembly, System.Threading.StackCrawlMark ByRef, Boolean, Boolean)
00000000204F8DC0 000007FEF23DBF61 System.Reflection.Assembly.InternalLoad(System.Reflection.AssemblyName, System.Security.Policy.Evidence, System.Threading.StackCrawlMark ByRef, Boolean)
00000000204F8E50 000007FEF23DC127 System.Reflection.Assembly.InternalLoad(System.String, System.Security.Policy.Evidence, System.Threading.StackCrawlMark ByRef, Boolean)
00000000204F8EB0 000007FEF2443A54 System.Reflection.Assembly.Load(System.String)
00000000204F8EF0 000007FF002D9FF7 System.Data.SqlServer.Internal.SqlAppDomain.LoadRawAssembly(Char*, Int32, IntPtr ByRef, System.Data.SqlServer.Internal.EClrReturnCode ByRef

=====

For the most current version of this article please see the following:

2709082 - After moving the System Center 2012 Configuration Manager SQL Site Database to another drive, creating a new Software Update package or a new application fails

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

WDS does not start on a PXE enabled remote DP in System Center 2012 Configuration Manager

$
0
0
We recently worked on an issue for a customer where WDS was not starting on a newly installed ConfigMgr 2012 remote DP that had PXE enabled. After some troubleshooting we discovered that when WDS was trying to load and initialize smspxe.dll, it could...(read more)

KB: When using prestaged media in Configuration Manager 2007, the partition name is set to the ID of the user who created it

$
0
0

imageHere’s a new Knowledge Base article we published this morning. This one discusses an issue where the partition name is set to the ID of the user who created it when using prestaged media in System Center Configuration Manager 2007.

=====

Symptoms

When creating and deploying prestaged media using System Center Configuration Manager 2007, when the WIM comes back from the OEM on a new target machine the label of the C: drive on the target machine is set to the ID of the user that created the media.

NOTE See the following for more information about prestaged media: http://blogs.technet.com/b/configurationmgr/archive/2011/01/11/how-to-stage-task-sequence-prestaged-media-on-a-hard-drive-in-configuration-manager-2007.aspx

Cause

This occurs because the media creation process manipulates the label of the C: drive by editing the label attribute in AutoRun.INF.

Resolution

Follow these steps to modify AutoRun.INF (which is inside the WIM) and remove the label attribute:

1. Run imagex.exe to mount the WIM (for example: WIM is e:\osd2\image3.wim):

C:
Cd\
Md mount
Cd\program files\windows aik\tools\x86
Imagex.exe /mountrw 1 e:\osd2\image3.wim c:\mount

2. Edit AutoRun.INF removing the lines containing Label= and Icon=:

Notepad c:\mount\autorun.inf

3. Run imagex.exe to unmount the WIM (make sure to exit out of c:\mount or a File in Use error may occur):

Imagex.exe /unmount /commit c:\mount

4. Update the WIM image on all Distribution Points with a new package source version.

5. Continue following the standard steps to create and deploy prestaged media per the article listed below in the More Information section.

More Information

How to stage Task Sequence Prestaged Media on a hard drive in Configuration Manager 2007 : http://blogs.technet.com/b/configurationmgr/archive/2011/01/11/how-to-stage-task-sequence-prestaged-media-on-a-hard-drive-in-configuration-manager-2007.aspx.

=====

For the most current version of this article please see the following:

2702735 - When using prestaged media in Configuration Manager 2007, the partition name is set to the ID of the user who created it

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Tips and Tricks: Resolving “Failed to create virtual directory” Error When You Install a Remote Distribution Point in System Center 2012 Configuration Manager

$
0
0
The Configuration Manager console has been greatly improved in System Center 2012 Configuration Manager, which enhances its usability. In addition to improvements in performance and layout, the console now supports a quicker way to monitor the status...(read more)

KB: The status of a failed upgrade to a shared Distribution Point may be displayed incorrectly as "Failed to upgrade distribution point" in System Center 2012 Configuration Manager

$
0
0

imageHere’s a new Knowledge Base article we published this morning. This one describes a potentially confusing status message you may see when upgrading a Distribution Point in System Center 2012 Configuration Manager.

=====

Symptoms

You try to upgrade a shared Distribution Point to a Microsoft System Center 2012 Configuration Manager Distribution Point. If the upgrade of the Distribution Point fails, the status on the Shared Distribution Points tab is displayed as follows:

Failed to upgrade distribution point.

You might expect the status on the Shared Distribution Points tab to be displayed as follows:

Failed to convert content.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

You can use the Configuration Manager console to upgrade Configuration Manager 2007 Distribution Points that you have shared with System Center 2012 Configuration Manager.

When you upgrade a shared Distribution Point, the Distribution Point is uninstalled from the Configuration Manager 2007 site. Then, the Distribution Point is installed as a System Center 2012 Configuration Manager Distribution Point that is attached to a primary or secondary site that you specify.

The upgrade process copies the migrated content that is stored on the Distribution Point and converts this copy to the System Center 2012 Configuration Manager single instance content store.

=====

For the most current version of this article please see the following:

2691560 - The status of a failed upgrade to a shared Distribution Point may be displayed incorrectly as "Failed to upgrade distribution point" in System Center 2012 Configuration Manager

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/


Deploying and configuring the Enhanced Mitigation Experience Toolkit (EMET) 3.0 with System Center Configuration Manager

$
0
0
You can use Configuration Manager to install the Enhanced Mitigation Experience Toolkit (EMET) 3.0 and subsequent configurations for applications to increase the security of applications on your managed systems. This blog walks you through the process...(read more)

Tips and Tricks: “Cannot find any applications in the specified file to import” Message when You Import an Application in System Center 2012 Configuration Manager

$
0
0
If you use the Import Application Wizard and see the error message dialog box in the following screenshot that says “Cannot find any application in the specified file to import”, it might be because of one of these reasons: The zip file...(read more)

KB: Changing a property of a deployment appears to not be saved in System Center 2012 Configuration Manager

$
0
0

imageHere’s a new Knowledge Base article we published this morning. This one describes an issue where it may seem that a change is not saved in ConfigMgr 2012.

=====

Symptoms

When modifying the Deployment options of a Distribution Point in the Selected Deployment Properties dialog box in Microsoft System Center 2012 Configuration Manager, the property change does not appear to have been saved.

Cause

This happens only when you have selected Make available to boot media and PXE in the Deployment Settings tab of the Selected Deployment Properties dialog box.

Resolution

This problem is only an issue with the settings that are visible in the user interface. The change is actually saved correctly in the database. You can run a custom report with a SQL query to verify your settings.

The below SQL query is an example which will show all task sequences with the Access content directly from a distribution point when needed by the running task sequence deployment option selected.

SELECT pkg.PackageID, pkg.Name, pkg.SourceSite,
CASE WHEN (adv.RemoteClientFlags & 0x00000008) = 0 THEN 0 ELSE 1 END AS RunFromDPInFastNetwork,
CASE WHEN (adv.RemoteClientFlags & 0x00000080) = 0 THEN 0 ELSE 1 END AS RunFromDPInSlowNetwork
FROM v_Advertisement AS adv
INNER JOIN v_Package AS pkg ON pkg.PackageID = adv.PackageID AND pkg.PackageType = 4
WHERE (adv.RemoteClientFlags & 0x00000008) <> 0 OR (adv.RemoteClientFlags & 0x00000080) <> 0

=====

For the most current version of this article please see the following:

2713465 - Changing a property of a deployment appears to not be saved in System Center 2012 Configuration Manager

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

KB: Failures with the Capture User State task or Task Sequence when using System Center 2012 Configuration Manager

$
0
0

imageHere’s a new Knowledge Base article we published. This one describes an issue where when performing hard-link migrations in System Center 2012 Configuration Manager, the User State Migration Toolkit (USMT) state store becomes much bigger than anticipated and potentially causes disk space problems.

=====

Symptoms

When performing hard-link migrations in System Center 2012 Configuration Manager, the User State Migration Toolkit (USMT) state store becomes much bigger than anticipated and potentially causes disk space problems. This also potentially causes the Capture User State task and Task Sequence to fail.

Cause

The Capture State task of System Center 2012 Configuration Manager has the ability to set the USMT option of /efs to either skip or copyraw via the option "Skip Files that use the Encrypting File System (EFS)". However there is no option to set it to hardlink. Without the ability to change the efs option to hardlink a hard-link to the EFS file is not created and instead a full copy of the file is created.

Resolution

Manually run USMT's scanstate.exe via a Run Command Line task which points to the USMT 4 package and provides a customized command line. An example command line using Task Sequence variables which performs a hard-link migration with the efs option set to hardlink would be:

.\%PROCESSOR_ARCHITECTURE%\scanstate.exe %OSDStateStorePath% /o /localonly /c /efs:hardlink /v:5 /l:%_SMSTSLogPath%\scanstate.log /progress:%_SMSTSLogPath%\scanstateprogress.log /i:.\%PROCESSOR_ARCHITECTURE%\migdocs.xml /i:.\%PROCESSOR_ARCHITECTURE%\migapp.xml /hardlink /nocompress %OSDMigrateAdditionalCaptureOptions%

=====

For the most current version of this article please see the following:

2713469 - Failures with the Capture User State task or Task Sequence when using System Center 2012 Configuration Manager

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

KB: System Center 2012 Configuration Manager Software Center does not launch on a Windows XP client if Terminal Services is disabled

$
0
0

imageHere’s a new Knowledge Base article we published. This one describes an issue where System Center 2012 Configuration Manager Software Center does not launch on a Windows XP client if Terminal Services is disabled.

=====

Symptoms

When starting Software Center on a Windows XP client, you receive the error "There is a problem showing the current status". Clicking more information you receive error code 0x80041001.

In ccmsdkprovider.log, the error is :

<![LOG[Failed to get domain name from WTS session 0, 0x800706a6]LOG]!><time="15:50:26.121-720" date="04-23-2012" component="CCMSDKProvider" context="" type="3" thread="264" file="ccmsdkprovider.cpp:3785">
<![LOG[GetUserCapability failed with error code 0x800706a6]LOG]!><time="15:50:26.121-720" date="04-23-2012" component="CCMSDKProvider" context="" type="3" thread="264" file="ccmsdkprovider.cpp:3266">

Error 800706a6 means that the RPC binding handle is invalid.

GetUserCapability calls Windows Terminal Server (WTS) functions to query session information for the Remote Desktop Session Host (RD Session Host) server. It can be used to query session information on local and remote desktop session host servers.

If Terminal Services is not running, calls to WTS functions fail.

Cause

WTS functions on Windows XP require that Terminal Services is running. This becomes an issue when the System Center 2012 Configuration Manager Software Center is launched on a Windows XP client when Terminal Server service is not running. If the Terminal Server service is not started, the Windows API call fails.

This is not an issue with operating systems later than Windows XP Service Pack 3 as the Windows API has been changed in these newer versions.

Resolution

Terminal Services must be enabled and the service started. Once that is done the Software Center will function on the Windows XP client as expected.

=====

For the most current version of this article please see the following:

2713471 - System Center 2012 Configuration Manager Software Center does not launch on a Windows XP client if Terminal Services is disabled

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Viewing all 715 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>