Just another WordPress.com site

Latest

Hello Windows 10. Have your seen 9?

Good morning! Today is the day where Microsoft is set to release the preview of their latest operating system after Windows 8.x. As you would expect, Windows 9 is just around the corner…not. Hit by surprise as many would expect, Microsoft is releasing their latest operating system…Windows 10!

Yes, don’t that make you wonder where did 9 go? From a blog release from Microsoft we have been told that the next release of Windows is so big that it deserves a perfect 10. From my view this release is set not only to incrementally fix the shortcomings of Windows 8 but to rethink the way an OS is to run on a slew of different devices today.

So some things that we can expect from Windows 10:-

(images courtesy from Microsoft blog release)

1. Welcome back, Start Menu.

If you’ve been using Windows 8 and 8.1 (that includes Windows Server 2012 and 2012 R2) you may have not experience the Start Menu (replaced with a Start screen) for some time now. It is back now, better and bigger…literally. The live tiles is not entirely gone though. You can still pin your favourite tiles to the Start Menu.

clip_image002

2. Windows, windows windows

The thing that made it more confusing for some users is the fact that there are 2 types of apps; a desktop app and a ‘metro’ app or I should call it modern UI app that runs full screen all the time optimized for touch on a tablet and touch devices. Now that too runs in a window. Now a modern UI app will run in a window complete with a top toolbar and the familiar 3 buttons to minimize, restore and close a window. The ability to pin it to the taskbar is still there, so that’s good.

clip_image004

3. Snapping a window is a snap

This is probably going to be my favourite. With larger resolution screens (mine on 3200 x 1800) we’ve got so much more screen estate that we can use. We used to be able to snap an open window to the left or right so that it resizes to take the left or right half of the screen. Now though, we can snap 4 app windows forming a quadrant for each app. Not only that, when an app is snapped, it suggests opened apps to be snapped in the available desktop space.

clip_image006

4. New button for task view

We’re all familiar with the Alt-Tab to switch between windows. Now there’s a new task view button when you hit it displays all the opened apps which you can select to bring it to the foreground or switch between desktops.

clip_image008

5. Hold on. Did I say switch desktops?

Yes I did. You can now have multiple desktops each for a different purpose perhaps. One for your personal stuffs and one where you put your recent work documents you’re working on.

clip_image010

For further reading follow the link below and there’s also a short video running through those features. Now if you’re like me and thinking how can I get my hands on this Technical Preview copy of Windows 10, currently there is a Windows Insider Program about to be open where you can sign up to be one of the first to test drive Windows 10 and hopefully provide feedback.

Where? Just go to http://preview.windows.com/. If you don’t see anywhere to sign up yet, wait a little longer as we’re all expecting it to be open really soon. Microsoft have been clear that this is a pre-release version and to expect it to be less refined as they are ironing out the rough edges.

 

 

 

Enjoy!!!

Configuration Manager Client Package source version keeps incrementing/increasing causing disk space to fill up in schedule.box

The first time I realized the problem is when I found that my replication isn’t going too well between my CAS and Primary. I soon found out that my disk space has run out on the partition ConfigMgr was installed on. That might be causing problem with replication, but what is causing my disk to fill up? Checking folder-by-folder I then found the offending folder that is filling up my drive. It was Program Files\Microsoft Configuration Manager\inboxes\schedule.box specifically the ‘tosend’ folder.

I did also realize that my server is busy transferring files. This can be seen by looking at the sender.log. I soon noticed it was the ConfigMgr agent package file and can be seen in the monitoring workspace that it is in the midst of updating all the DPs. Shockingly I noticed the version number of the Configuration Manager Client Package has gone up close to 200, notice version 180 from the distmgr.log.

Found notification for package ‘CL100003’    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:53 AM    7140 (0x1BE4)
Used 0 out of 3 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:53 AM    7140 (0x1BE4)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:53 AM    6628 (0x19E4)
Starting package processing thread, thread ID = 0x2304 (8964)    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:53 AM    7140 (0x1BE4)
Starting package processing thread, thread ID = 0x1A60 (6752)    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    7140 (0x1BE4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    7140 (0x1BE4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=<FQDN> SITE=CAS PID=2644 TID=8964 GMTDATE=Wed Sep 10 17:37:54.312 2014 ISTR0="Configuration Manager Client Package" ISTR1="CL100002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CL100002"    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    8964 (0x2304)
Start updating the package CL100002…    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    8964 (0x2304)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=CL100002, Version=180, Status=2300    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    8964 (0x2304)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=<FWDN>SITE=CAS PID=2644 TID=6752 GMTDATE=Wed Sep 10 17:37:54.344 2014 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="CL100003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CL100003"    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Start updating the package CL100003…    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Taking package snapshot for package CL100002 from source \\<FQDN>\SMS_CAS\Client    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    8964 (0x2304)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=CL100003, Version=180, Status=2300    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Taking package snapshot for package CL100003 from source \\<FQDN>\SMS_CAS\ClientUpgrade    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The size of package CL100003, version 180 is 1576 KBytes    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Successfully created RDC signatures for package CL100003 version 180    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Creating hash for algorithm 32780    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The hash for algorithm 32780 is D6279C75363ECFBE0F4A64447E472F512261393FFBE6246AB153ACEF41C53094    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The RDC signature hash for algorithm 32780 is 9CEFAE33CC2B4475D5B67C8C6046A48834B03C292B59C16222070B6161168017    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
STATMSG: ID=2376 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=<FWDN> SITE=CAS PID=2644 TID=6752 GMTDATE=Wed Sep 10 17:37:54.600 2014 ISTR0="CL100003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CL100003"    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=CL100003, Version=180, Status=2376    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The source for package CL100003 has changed or the package source needs to be refreshed    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Adding these contents to the package CL100003 version 180.    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The Package Action is 1, the Update Mask is 32 and UpdateMaskEx is 0.    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Use drive E for storing the compressed package.    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Successfully created/updated the package CL100003    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)

 

This happened during my hierarchy expansion from a standalone primary to a CAS and multiple primaries. The Configuration Manager Client Package though still the same packageID had its source path changed to the CAS server UNC path and that may have triggered a package update. Trying to stop the DP transfer by deleting the package or removing content didn’t work because it will be grayed out.

image

In order to be able to do that you need to go into SQL. First create 2 new packages for the Configuration Manager Client Package and Configuration Manager Client Upgrade Package. They will be having new package IDs. Note them down!

Then using the SQL Server Management Studio console find out what is your existing ClientDeploymentSettings. Enter the below statement in your new query window.

select * from CM_CAS.dbo.ClientDeploymentSettings

 

This wil return the result of your FullPackageID and UpgradePackageID. Next we will update it to the new packageID of the new packages you’ve just created. Use the below statements

update CM_CAS.dbo.ClientDeploymentSettings set FullPackageID = ‘<new package ID>’ where FullPackageID = ‘<old package ID>’

 

Now do the similar for the UpgradePackageID

update CM_CAS.dbo.ClientDeploymentSettings set UpgradePackageID = ‘<new upgrade package ID>’ where UpgradePackageID = ‘<old upgrade package ID>’

 

After this you can go ahead and remove the package from the DPs. It will not be grayed out anymore.

If this still does not solve your problem especially after a reboot (this might re-occur after a reboot), investigating further you will find this in your hman.log.

HandleRBACPermissions : Check if there is request.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
End sync rbac permissions.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
Update site server active directory informtion into DB    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
Handle auto-upgrade client configuration changes    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
Update auto-upgrade client configurations    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: client.acu file was found. client upgrade packages need to be updated.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Current client upgrade settings are: FullClientPackageID=CL100002, ClientUpgradePackageID=CL100003, ClientUpgradeProgramName=Configuration Manager Client Upgrade Program, ClientUpgradeAdvertisementID=CL120000, ClientUpgradeVersion=5.00.7958.1000.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully requested package CL100002 to be updated from its source.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully requested package CL100003 to be updated from its source.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully updated packages CL100002 and CL100003    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Client upgrade command line will be modified to ccmsetup.exe /AutoUpgrade /UpgradePackageVersion:240    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
Updating supported platforms for auto-upgrade client program.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully updated program Configuration Manager Client Upgrade Program of package CL100003 with new command line: ccmsetup.exe /AutoUpgrade /UpgradePackageVersion:240    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully modified the command line for client upgrade program Configuration Manager Client Upgrade Program in package CL100003.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)

 

Realize that client.acu file is found in the Program Files\Microsoft Configuration Manager\inboxes\hman.box path and that is what is instructing the package to be updated. It is a file with 0kb. So go ahead and delete that file from your server and that should stop your Configuration Manager Client Package from wrongly self updating itself.

 

 

 

Enjoy!!!

ConfigMgr 2012 Pre-requisites Installation Tool

Have you been trying to remember the long list of pre-requisites components needed for each ConfigMgr server role? Take a look at this. Then I’ve been documenting steps to make it easier to go about it. Then moved to using PowerShell? Nowadays I’ve been actively using this for most of my ConfigMgr installations. This new version by Nickolaj Andersen, supports ConfigMgr 2012 R2. Now it has tabs for each ConfigMgr server you’re trying to prepare for; CAS, Primary, Secondary etc. So no more trying to remember the list of pre-reqs? Maybe? Download version 1.3.0 here. There is also an older version still made available for ConfigMgr 2012 SP1 here.

 

 

 

Enjoy!!!

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!!!

Follow

Get every new post delivered to your Inbox.

Join 66 other followers