Just another WordPress.com site

Latest

Failed to Validate an MP from registry (8004005) and Failed to send Package State Messages to Site Server from Remote DP when running ExtractContent.exe for PrestageContent – SCCM 2012

So, I was trying to use the Prestaged Content File to send over a relatively large package over to a DP without transferring it over the wire. If you’ve done previous versions of SCCM, this is similar to courier sender. It enables administrators to send packages to a DP without using the any network bandwidth which is good for situations where bandwidth is scarce or if it takes too long to transfer it over a small bandwidth.

When I completed running the extractcontent.exe command line tool to decompress and extract my .PKGX file generated from my Primary Site server I get errors in my PrestageContent.log which is normally located at \SMS_DP$\sms\logs in the prestage DP itself.

 

Begin ====> Mon Dec 16 2013 18:17:36    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
The following parameters were passed on command line:     PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
    /P – Full path to a prestaged file or to a folder containing one or more such files: ‘C:\Prestaged content file\Win7SP1x64.pkgx’    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
    /F – Force prestaging of content even when it already exists on the site    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
Detecting if a distribution point role exists on this machine    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
Client is set to use HTTPS when available. The current state is 224.    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
Set media certificate in transport    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
Set authenticator in transport    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
unknown host (gethostbyname failed)    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
sending with winhttp failed; 80072ee7    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
Failed to get information for MP: http://SetE-CM.SetE.local. 80072ee7.    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
Failed to validate an MP from registry: http://SetE-CM.SetE.local. 80004005    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
Checking content library on local DP    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
Content library: path=’C:\SCCMContentLib’, usable drives=’C:\’    PrestageContent    12/16/2013 6:17:36 PM    3248 (0x0CB0)
============ Content meta data begin ===================    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
File "C:\Prestaged content file\Win7SP1x64.pkgx"    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
Content type: "Classic"    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
Content modified: 16/12/2013 08:01:40    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
Disk space required: 5021 MB    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
Packages:     PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
  Package=MK200015.1, SMB=0    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
Content Names:    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
    "Win7SP1x64"    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
============ Content meta data end =====================    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
Content library already contains content MK200015.1    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
Free space on the content library drive is 20286 MB    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
The best drive on this remote DP is found to be C: (free space 20286 MB)    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
No branch cache registry entries found.    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
Uncompressing C:\Prestaged content file\Win7SP1x64.pkgx to C:\Prestaged content file\Win7SP1x64.pkgx.temp    PrestageContent    12/16/2013 6:18:16 PM    3248 (0x0CB0)
Content Library: C:\SCCMContentLib    PrestageContent    12/16/2013 6:19:16 PM    3248 (0x0CB0)
Extracting from C:\Prestaged content file\Win7SP1x64.pkgx.temp    PrestageContent    12/16/2013 6:19:16 PM    3248 (0x0CB0)
Extracting package MK200015    PrestageContent    12/16/2013 6:19:16 PM    3248 (0x0CB0)
Extracting content MK200015.1    PrestageContent    12/16/2013 6:19:16 PM    3248 (0x0CB0)
Content definition already exists: \\?\C:\SCCMContentLib\DataLib\MK200015.1    PrestageContent    12/16/2013 6:21:33 PM    3248 (0x0CB0)
Generating signature files to path C:\SMSSIG$    PrestageContent    12/16/2013 6:22:04 PM    3248 (0x0CB0)
Management point name is not defined    PrestageContent    12/16/2013 6:22:04 PM    3248 (0x0CB0)
Site Code: ‘MK2’    PrestageContent    12/16/2013 6:22:04 PM    3248 (0x0CB0)
DP server: ‘E-WIN7CMDP.SetE.local’    PrestageContent    12/16/2013 6:22:04 PM    3248 (0x0CB0)
NAL Path: ‘["Display=\\E-WIN7CMDP.SetE.local\"]MSWNET:["SMS_SITE=MK2"]\\E-WIN7CMDP.SetE.local\’    PrestageContent    12/16/2013 6:22:04 PM    3248 (0x0CB0)
some DP settings are not defined.    PrestageContent    12/16/2013 6:22:04 PM    3248 (0x0CB0)
Failed to send package state messages to site server from remote DP.    PrestageContent    12/16/2013 6:22:04 PM    3248 (0x0CB0)
End ====> Mon Dec 16 2013 18:22:04    PrestageContent    12/16/2013 6:22:04 PM    3248 (0x0CB0)

Solution:

The problem that I found was that my DP didn’t have access rights to my Site Server. What has to be done was to add the DP computer account as an administrator to my Site Server. I should have caught that earlier when I saw “Failed to validate an MP from registry: http://SetE-CM.SetE.local. 80004005”. The DP was not able to send package state messages to site server to tell it that the extraction was complete and that it can now use the content. Also to my oversight that 80004005 normally points to an “access denied” error.

 

 

 

Enjoy!!!

Failed to install a new Distribution Point (error 0x800706BA)

When I was trying to install an additional distribution point for a ConfigMgr 2012 R2 environment my installation failed with the following entries in the distmgr.log file.

CWmi::Connect() failed to connect to \root\SCCMDP">\\<servername>\root\SCCMDP. Error = 0x800706BA    SMS_DISTRIBUTION_MANAGER    12/3/2013 11:35:57 AM    2660 (0x0A64)
STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=<servername>SITE=PS1 PID=3688 TID=2660 GMTDATE=Tue Dec 03 03:35:57.350 2013 ISTR0="["Display=\\<servername>\"]MSWNET:["SMS_SITE=PS1"]\\<servername>\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\<servername>\"]MSWNET:["SMS_SITE=PS1"]\\<servername>\"    SMS_DISTRIBUTION_MANAGER    12/3/2013 11:35:57 AM    2660 (0x0A64)
GetWMIObject – Failed to connect to root\SCCMDP on ["Display=\\<servername>\"]MSWNET:["SMS_SITE=PS1"]\\<servername>\. Error code: 0x800706BA    SMS_DISTRIBUTION_MANAGER    12/3/2013 11:35:57 AM    2660 (0x0A64)
Translated server name <servername> to <domain name>\<servername>.    SMS_DISTRIBUTION_MANAGER    12/3/2013 11:35:57 AM    2660 (0x0A64)
CWmi::Connect() failed to connect to \\<servername>\root\SCCMDP. Error = 0x800706BA    SMS_DISTRIBUTION_MANAGER    12/3/2013 11:35:57 AM    2660 (0x0A64)
STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=<servername> SITE=PS1 PID=3688 TID=2660 GMTDATE=Tue Dec 03 03:35:57.391 2013 ISTR0="["Display=\\<servername>\"]MSWNET:["SMS_SITE=PS1"]\\<servername>\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\<servername>\"]MSWNET:["SMS_SITE=PS1"]\\<servername>\"    SMS_DISTRIBUTION_MANAGER    12/3/2013 11:35:57 AM    2660 (0x0A64)
CWmiDpRegistry::WmiOpenEx: Failed to connect to WMI namespace root\SCCMDP on machine <servername>SMS_DISTRIBUTION_MANAGER    12/3/2013 11:35:57 AM    2660 (0x0A64)

It looks like it is having difficulty to connect to a certain WMI namespace even though generally it could connect to the server and there’s nothing wrong with connectivity. Checking further on the console when you’re trying to install a package to that DP will give you the following error “failed to distribute content” and a description that says that details will be available after the server finishes processing the messages.

image

 

So the way to solve this is to fix the WMI namespace by parsing a MOF file into the target server that you’re trying to install DP on. Do this by first getting the smsdpprov.mof file from your installation of ConfigMgr and copying it into your target DP server. Typically this is located at <drive:>\Program Files\Microsoft Configuration Manager\bin\X64 in your primary site server. Then all you need to do is to run the below command using the command prompt. Remember to ‘run as administrator’ and change directory to the location where you copied the smsdpprov.mof to but I don’t really need to tell you that :)

mofcomp.exe smsdpprov.mof

clip_image002

 

 

 

Enjoy!!!

Enable Deduplication on your Windows 8.1

This is just an update to my past post on how to enable data deduplication on Windows 8 (which normally is only available on Windows Server 2012). It took me awhile but I’ve not had time to look into this. The good news is it’s here thanks to a blogger Mailspintoys for the files. I’ve made copies of those files and shared it on my skydrive too but you could very much also download it from his blog.

One reminder though, this didn’t work for me when I was testing it on a VM and it only works if you installed Windows 8.1 physically, at least from what I’ve tried. That means you have to take the dive into Windows 8.1 without trying it around on a VM. Credit goes to Corne van Bochove for the valuable sharing in my past post and Mailspintoys for the extracted files.

The new command line to execute is as below:-

dism /online /add-package /packagepath:Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab /packagepath:Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab  /packagepath:Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab /packagepath:Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab  /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab

dism /online /enable-feature /featurename:Dedup-Core /all

 

Basically the only difference from the previous one is the version number changed from 6.2.9200 to 6.3.9600. Hope you enjoy the feature as much as I did. For a more complete post on it go to my previous blog on this. http://weikingteh.wordpress.com/2013/01/15/how-to-enable-data-deduplication-in-windows-8/

 

 

 

Enjoy!!!

Uninstall/Remove Office 2013 with ConfigMgr 2012

Right, recently I’ve just posted on how to get ConfigMgr 2012 to deploy Office 2013. Now I want to show you how to uninstall Office 2013 using ConfigMgr 2012. You’re thinking, just use the /uninstall switch and that’s it but I’ll show you how to automate and silently remove Office 2013.

You’re almost correct to just put an /uninstall switch at the back of the setup.exe command line in ConfigMgr console. However to make it silent you need an .XML file. First open up Notepad or any text editing tool that you have and then enter the following text:-

<Configuration Product="ProPlusr">

<Display Level="basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" />

</Configuration>

 

Note that you either use the ProPlus or ProPlusr depending on whether you’re using the VL media or the Non-VL media. You could also change the Display Level to “none” if you like it and the CompletionNotice to “no” if you wish. That’s totally up to you. Now, save the file as SilentUninstallConfig.xml into the proplus.ww folder or the proplusr.ww folder, again depending on the media you’re using.

The last thing to do is to change the Uninstall program command line to reference the .XML file that you’ve just created. To do this enter the following into the Uninstall program text box.

setup.exe /uninstall ProPlusr /config .\ProPlusr.WW\SilentUninstallConfig.xml

image

Again, remember your path and Product ID; it is either ProPlus or ProPlusr depending on the media you’re using. And that’s about it!

 

 

 

Enjoy!!!

Windows 8.1 RTM and Windows Server 2012 R2 RTM is available for download now on MSDN and TechNet

If you’ve not yet heard it from your Facebook friends yet, here it is! Download was available as of last night. For those without access to MSDN or TechNet no worries. You’ll get your hands on it soon enough…18th October 2013 when it is officially available to the public. I’m at 21% of the download now. Where are you at? :)

 

 

 

Enjoy!!!

Comparison of SMS 2003 vs SCCM 2007 vs SCCM 2012

So a good friend recently asked me for a version comparison of the ConfigMgr 2012 and the previous versions, so here’s my take on it. I know there are gaps but I can’t think of every single thing here. Ultimately these are the same product just from a different generation :). The huge change came between ConfigMgr 2007 and ConfigMgr 2012…I know some of you call it SCCM. So this is just a quick glance on the differences between these versions. This compilation was based out from Raymond Chou’s blog post with much additions.

 

Features SMS 2003 ConfigMgr 2007 ConfigMgr 2012
Hardware & Software Inventory Check mark symbol Check mark symbol Check mark symbol
     Define Inventory Collection Check mark symbol Using SMS_def.mof file Check mark symbol Using SMS_def.mof file Check mark symbol GUI
Software Distribution Check mark symbol Check mark symbol Check mark symbol
   Computer-based Targeting Check mark symbol Check mark symbol Check mark symbol
   Self-service Portal     Check mark symbol
   User Only Collection     Check mark symbol
   Device Only Collection     Check mark symbol
   User-Device Affinity     Check mark symbol
   State-based Application Management     Check mark symbol
   App-V Package Distribution   Check mark symbol Check mark symbol
   Windows Store Package Distribution     Check mark symbol
   Windows Phone Application Distribution     Check mark symbol
   Windows Mobile Cabinet Package Distribution   Check mark symbol Check mark symbol
   iOS .ipa Package Distribution     Check mark symbol
   iOS Application from AppStore     Check mark symbol
   Android .apk Package Distribution     Check mark symbol
   Android Application from Google Play     Check mark symbol
   Auto-install Dependant Application Check mark symbol*P Cannot check existence of dependant app before installing Check mark symbol*P Cannot check existence of dependant app before installing Check mark symbol
   Application Requirement Rules     Check mark symbol
   Shared Cache     Check mark symbol
   User-Triggered Un-installation     Check mark symbol
Hierarchy      
   Boundary Groups     Check mark symbol
Software Updates Management ITMU WSUS WSUS
   3rd Party Application   Check mark symbol Check mark symbol
   Automatic Deployment Rules     Check mark symbol
   Automatic clean-up of Superseded and Expired Updates     Check mark symbol
Software Metering Check mark symbol Check mark symbol Check mark symbol
Policy Targeting Site Site Collection
Remote Control Check mark symbol Check mark symbol Check mark symbol Ctrl-Alt-Del
Reporting Check mark symbol Web Check mark symbol Web + SQL Reporting Services Check mark symbol SQL Reporting Services
Agent-based Management Check mark symbol Check mark symbol Check mark symbol
Active Directory Integration Check mark symbol Check mark symbol Check mark symbol
   Automatic Site Boundary Discovery     Check mark symbol
   Cross-forest Management     Check mark symbol
   User Discovery   Check mark symbol Check mark symbol
   Computer Discovery Check mark symbol Check mark symbol Check mark symbol
   AD Group Discovery   Check mark symbol Check mark symbol
Operating System Deployment   Check mark symbol Check mark symbol
   Offline Image Servicing     Check mark symbol
   Task Sequence   Check mark symbol Check mark symbol
   Automatic Driver Injection   Check mark symbol Check mark symbol
   Integration with MDT   Check mark symbol Check mark symbol
Automatic Detection of Configurations and Settings   Check mark symbol known as Desired Configuration Management Check mark symbol known as Settings Management
   Automatic Remediation     Check mark symbol
Internet-based Client Management Check mark symbol Check mark symbol Check mark symbol
Maintenance Window   Check mark symbol Check mark symbol
Intel vPro Integration   Check mark symbol SP1 Check mark symbol
Role-based Access Control     Check mark symbol
Define User Scope     Check mark symbol
Power Management   Check mark symbol R3 Check mark symbol
   Ability for Users to Opt-out     Check mark symbol
Device Management   Check mark symbol Check mark symbol
   Windows Mobile   Check mark symbol Check mark symbol
   Windows Phone     Check mark symbol
   Apple iOS     Check mark symbol
   Google Android     Check mark symbol

 

Note: *P = Partial

Deploying Office 2013 with ConfigMgr 2012

Okay, so here’s my run on this topic though not something new. First you need to prepare the installation media of Office 2013. The only supported media is the Volume License media so make sure you’ve got the right media. However if you’ve got another media that is not VL, don’t worry you can still make do with it. You will need to download the Office 2013 Administrative Template files (ADMX/ADML) and Office Customization Tool. What you really need here is the Office Customization Tool. Now, copy all the contents of the media to a shared folder. If you’ve got both the 32-bit and the 64-it media, ensure that you put them in separate folders.

image

 

Double-click to launch either the 32-bit or 64-bit version.

image

 

Select the check-box and then click Continue.

image

 

Browse to the location where you’ve copied the contents of the Office 2013 media to then place to extract it to the respective folders; 32-bit to the \\Source\Office 2013 Pro Plus\x86 and the 64-bit to the \\Source\Office 2013 Pro Plus\x64.

image

 

Once you’ve extracted it you’ll notice 3 new folders created.

image

 

Now, go ahead and kick-off the setup.exe using the /admin switch.

image

 

If this is the first time you’re doing this, select the default to create a new Setup customization file.

image

 

The Office customization wizard appears. You can customize almost all settings but in this writing we’re only gonna configure a few.

image

 

Select Licensing and user interface. Here we’ll accept the terms in the License Agreement and change the Display level to Basic. Select the check-box beside Suppress modal and No cancel. If you’re not using a KMS server to activate your copy of Office, then alternatively you can enter the MAK key to activate your copy of Office.

image

 

Select the Set feature installation states. The other thing I always like to do is to select the components that I want installed. For example if you only want to install Word, Publisher and Excel without PowerPoint, then you can do so here. You can see below that I’ve made my selections.

image

 

There’s a whole lot of other things you can customize here but let’s leave it as this for now. Now you gotta save this settings, so go to File > Save and go ahead and save the file. The .MSP that is created must be place in the Updates folder where you copied you media contents to.

image imageimage

 

You’re almost done. Now you have to create or import it as an application in the ConfigMgr console. You need to browse to \Software Library\Overview\Application Management\Applications. Here you will right-click on Applications and then select Create Application.

image

 

Here go ahead and browse to the location where you copied your media content to. Make sure it in an UNC path and select the proplusww.msi file in the proplus.ww folder; \\SetE-cm\source\Office\x64\proplusr.ww\proplusrww.msi then click Next.

image

 

The information about the application is imported so just click Next.

 image

 

Here you can populate the information for administrator comments, manufacturer, software version and so on. At the Installation program: text box, delete the existing msiexec /i "proplusrww.msi" /q and replace it with setup.exe. Leave the other as default then click Next to proceed.

image

 

At the Summary page, click Next.

image

 

The application is created. Click the Close button.

image

 

Now you can see the application that you’ve just created. There are some settings in there that you need to change. Click on the Deployment Type tab at the bottom of the screen, then right-click on the MSI Deployment Type and then select Properties.

image

 

Go to the Content tab and at the Content location text box, remove proplus.ww or proplusr.ww so it should look something like \\SetE-cm\source\Office\x64\

image

 

Go to the Programs tab and then on the Uninstall program: text box, remove the existing content and then enter setup.exe /uninstall. That should be it so click OK to close the pop up.

image

 

Now to deploy the application you’ve just created. Simply right-click on the application you want to deploy and then select Deploy.

image

 

In the General page, click the Browse button to select the collection.

image

 

Select the target User Collection. In my case I’ve selected the All Users collection. You could also deploy it to a Device Collection too if you wanted. Click Next at the General page to proceed.

image

 

At the Content page, click the Add button and then select Distribution Point. Since I only have only one Distribution Point I’ll go ahead and select that but you can select any number of Distribution Points you would like to distribution this application content.

image image

 

At the Deployment Settings page, click Next to proceed.

image

 

At the Scheduling page, click Next.

image

 

At the User Experience page, click Next.

image

 

At the Alerts page, click Next.

image

 

At the Summary page, click Next.

image

 

At the Completion page, click Close.

image

 

Now let’s take a look at how it looks like on the client end. From your Windows client machine, open up your Internet Explorer and then browse to http://<ConfigMgr Server Name>/CMApplicationCatalog/

image 

 

You should see the application that you’ve just deployed. Click the Install button, and then when asked if you are sure that you want to install the selected application, click Yes.

image

 

Here you can see that the installation has begun.

image

 

This is the basic UI you have chosen during the Office Customization Tool wizard. The user can only observe the installation process but cannot interfere with it.

image

 

After you give a few moments, ConfigMgr will notify you that the installation has completed and you now have Office 2013 installed. Happy deploying!

image

 

 

Enjoy!!!

Follow

Get every new post delivered to your Inbox.

Join 62 other followers