You are browsing the archive for ConfigMgr 2012 SP1.

Windows Phone 8 not enrolling with the “Support Tool for Windows Intune Trial Management of Window Phone 8”

8:47 am in ADFS, Cloud, CM12, ConfigMgr 2012 SP1, intune, SCCM 2012 SP1, Windows Intune by Kenny Buntinx [MVP]

 

At a customer and integrating/managing Windows Phone 8 with Windows Intune and System Center Configuration Manager 2012 SP1 ? Using the Support Tool for Windows Intune Trial Management of Window Phone 8 (can be downloaded at http://www.microsoft.com/en-sg/download/details.aspx?id=39079) ?

The Support Tool for Windows Intune Trial Management of Window Phone 8 facilitates Microsoft System Center 2012 Configuration Manager admins to try out Windows Phone 8 software distribution scenarios during the Trial period.

However we couldn’t get our Windows phone 8 enrolled. It always came back with the following error on the phone : “We weren’t able to set up this company account on your phone”.

Verify the following before going forward :

  • If Are you using ADFS , check my previous blog post “Troubleshooting ADFS 2.1 Services for Windows Intune (WaveD)”.
  • Have you synced your AD accounts to Azure AD? Is dirsync working correctly ? Check from Azure AD that you see your local AD users there.
  • Make sure the UPN is set correctly to your Domain ( SCUG.be instead of scug.onmicrosoft.com)
  • Set CNAME to manage.microsoft.com

SNAGHTMLfb3cfe6

  • Reset your Users password. Because the user must reset the password after the first logon, logon to e.g. portal.manage.microsoft.com with the user account, before enrolling the device.
  • It is important that you first synchronize your AD users to Azure and after that add the user account to user collection that is allowed to enroll the devices. If you first add the user to the collection and the new user is not in Azure AD, you need to wait up to 24 h. (Tnx to my fellow MVP Panu Sauko!)
  • If you get the latter error message, change the language & regional settings of your mobile phone to en-US and try to enroll again. (Tnx to my fellow MVP Panu Sauko!)

Going down in the logs , by the way very difficult on a Windows phone 8 or Windows Intune side , the only option was to look into the System Center Configuration Manager Log files .

Looking in the dmpdownloader.log and found the following line appearing every time I tried to enroll the WP8 device . Strange .

ERROR: Service health log: WP appStoreURI is missing for account 73dab792-979c-40be-947b-b7c8040e725b and userId ******************************33d16d

image

Solution :

Apparently to that message , it seems that we have Certificate issues on the Company portal . After re-registering the steps below , it works . Before it executed also successfully ,and I thought everything was OK , but I was wrong. So if you have the above error message “ Service health log: WP appStoreURI is missing for account “ , it means there is something wrong with your company portal and signed certificates.

  • Step 1 : Disable the Windows Phone 8 support on the intune connector :

image

1.  Create your application “Company portal” that is included in the toolkit.

2. The first step to enable the management of Windows Phone 8 devices is to run the script that is included  cscript ConfigureWP8Settings.vbs <server> QuerySSPModelName . It is important to notate the Scope_ID<GUID> information as it will be used in the next step.

3.  Next we need to run the script again but this time in Save mode with the SSP name to populate the necessary certificate information that enables Windows Phone 8 Management.  The command will will use this time is: cscript ConfigureWP8Settings.vbs <server> SaveSettings <Company Portal name> where <Company Portal name> is the output for Model Name from the earlier step.

4.  After completion of the steps above, you can now verify that Windows Phone 8 device management is enabled.  

image

Now you can enroll your Windows Phone 8 devices in your Windows Intune Unified Trial Account. It works like a charm now .

image

Hope it Helps ,

Kenny Buntinx

MVP enterprise Client Management

Prepare to Install ADFS 2.1 Services to have SingleSignOn (SSO) in Windows Intune (WaveD) – Part 2

12:09 pm in ADFS, Cloud, CM12, ConfigMgr 2012 SP1, intune, SCCM 2012 SP1, Server 2012, WaveD, windows inune by Kenny Buntinx [MVP]

 

In my previous blog posts “Prepare to Install ADFS 2.1 Services to have SingleSignOn (SSO) in Windows Intune (WaveD) – Part 1” I explained the genaeral design and concept for setting up SSO with ADFS  at “http://scug.be/sccm/2013/07/04/prepare-to-install-adfs-2-1-services-to-have-singlesignon-sso-in-windows-intune-waved/

This article takes it step-by-step through initializing a new domain in Windows Intune WaveD , its verification, and configuration for single sign-on. This guide will show how to perform these steps on Windows Server 2012 with AD FS 2.1.

Again our design we are going to follow :

SNAG-0333

Determine the ADFS Farm Name

We really need to get this information sorted first, because our certificate requests will be based on the FQDN of the farm name, and it isn’t possible to install ADFS services without a certificate.

We’ll use “Federation.scug.be” – this name will be used by by Windows Intune federation services. This certificate absolutely must be issued by a public CA.

Request a Certificate

Really quick overview of ADFS certificates: there are three certificates used by ADFS; one is used for server authentication and the remaining two certificates are used for ADFS token signing and verification

For best practice and supportability this certificate should NOT a wildcard certificate. However my wildcard certificates were working flawless, but if you go that way and something does not work later down the road, your support options may be limited at this time.

Service Account for ADFS Federation Service

Next, we will create a service account for the purpose of installing and running ADFS Federation Service. This service account will be used to perform initial installation of the service as well as the WID SQL databases. During this initial installation, the service creates certificate containers in Active Directory, as well as SPN records for the shared IIS pool identity. To perform these tasks, the service account must be at least a Domain Admin.

Install ADFS Service on the First Windows Server 2012 Server (FED1PRD.SCUG.BE)

Prerequisites :

  • Make sure that you installed the ADFS Services thru “Add Roles and Features”.
  • Make sure you have copied your *.SCUG.be certificate on your ADFS Servers
  • Make sure they are added to the domain
  • Your Active Directory Domain must be in Windows 2003 mixed or native mode.

1. Open the wizard and select “Create a new Federation Wizard” …

image

2. Provide your SSL certificate and Federation Service Name …

image

3. Provide your Service Account and password …

ADFS_3

4. Click Next tot continue after reviewing…

image

5. When everything is ok , click close to close the wizard.

clip_image002

Install ADFS Service on the Second Windows Server 2012 Server (FED2PRD.SCUG.BE)

1. Open the wizard and select “Add a federation server to an existing Federation Service” …

clip_image002[5]

2. Specify your primary federation Server name and your ADFS service account .

image

3. Click next to install and finish

clip_image002[7]

Important :

Create a host file on the FED1PRD.SCUG.BE and FED2PRD.SCUG.BE with the following line:

image

Now your ADFS Farm is installed and configured correctly.Now let’s show you how to introduce an AD FS Proxy Server.

In addition to adding two federation server proxies, you must make sure that your perimeter network can also provide access to a Domain Name System (DNS) server and to a second hardware Network Load Balancing host. The second NLB host must be configured with an NLB cluster that uses an Internet-accessible cluster IP address, and it must use the same cluster DNS name (federation.SCUG.be) setting as the previous NLB cluster that you configured on the corporate network (Federation.scug.be). The federation server proxies should also be configured with Internet-accessible IP addresses.

Note: All the servers / clients communication is established over port 443, make sure that port 443 is allowed from and to the internal AD FS host server to the AD FS proxy servers, as well from the Internet to the AD FS proxy servers

 

Importing the Certificate on FED1PRD.SCUG.BE and FED2PRD.SCUG.BE

After that , Import your *.SCUG.BE certificate on FED1PRD.SCUG.BE and FED2PRD.SCUG.BE in your website as described below :

After the certificate has been imported, you’ll want to verify it by going back to Server Certificates in IIS.

image

Next, you’ll need to add the Certificate to the Default Web Site.  With the Default Web Site Selected click Bindings.

image

Click Add

image

Choose Type https, IP addresss All Unassigned, and Port 443.  Then select the newly imported certificate and click Ok.

image

The site bindings should now look like:

image

 

Install ADFS Proxy Servers on Windows Server 2012 Server (ADFSPROXY01 – ADFSPROXY02)

1. Select “ADFS Federation Services Proxy” thru “Add Roles and Features”.

clip_image002[9]

2. Leave the defaults selected and select “Next”

clip_image002[11]

3.Hit “install” button.

clip_image002[13]

Important :

Create a host file on the ADFSPROXY01 and ADFSPROXY with the following line:

 image

Note: All the servers / clients communication is established over port 443, make sure that port 443 is allowed from and to the internal AD FS host server to the AD FS proxy servers, as well from the Internet to the AD FS proxy servers

 

Importing the Certificate on ADFSPROXY01 and ADFSPROXY02

After that , Import your *.SCUG.BE certificate on ADFSPROXY01 and ADFSPROXY02 in your website as described below :

After the certificate has been imported, you’ll want to verify it by going back to Server Certificates in IIS.

image

Next, you’ll need to add the Certificate to the Default Web Site.  With the Default Web Site Selected click Bindings.

image

Click Add

image

Choose Type https, IP addresss All Unassigned, and Port 443.  Then select the newly imported certificate and click Ok.

image

The site bindings should now look like:

image

 

DNS Configuration

  • Configure internal DNS to point to the federation hosts cluster (NLB) IP
  • Set up a host (A) record for the domain (federation.scug.be) on a public-facing DNS server for external name resolution to point to the proxy servers cluster (NLB)

Optional – in case the proxy servers doesn’t have DNS connectivity to the internal DNS server, you can configure the host file (see above topic) on each server to resolve the AD FS host servers name

 

The end

Now your ADFS Farm is completely installed and configured correctly.

This brings us to the end of this post. In the next few posts, we’ll cover additional configuration and troubleshooting steps and bring this Windows Intune SSO / ADFS 2.1 infrastructure on Windows Server 2012 to a usable state.

Stay Tuned !

 

Hope it Helps ,

Kenny Buntinx

Enterprise Client MVP

Prepare to Install ADFS 2.1 Services to have SingleSignOn (SSO) in Windows Intune (WaveD) – Part 1

1:42 pm in ADFS, best practices, con, ConfigMgr 2012 SP1, intune, scc, SCCM 2012 SP1, Windows Intune by Kenny Buntinx [MVP]

 

With the SP1 release of System Center 2012 Configuration Manager, we now have the ability to connect to Windows Intune to manage mobile devices via the Internet. This allows you to use the Configuration Manager console to provision mobile devices, apply policy, and target apps to mobile devices even when those devices are not connected to the corporate network.

To provide users with an integrated sign-on experience (and reduce the need for administrators to manage two passwords for users) it is highly recommended that you deploy ADFS. ADFS provides the capability for a cloud server to leverage on-premise Active Directory credentials.

To deploy and configure ADFS 2.1 (server 2012) , follow the steps outlined below. This blog will cover the configuration and deployment work needed to successfully connect their device with corporate credentials . Before you install ADFS 2.1 on Windows Server 2012, you have to think through some of the requirements.

The benefits of implementing ADFS:

  • Improves user productivity by enabling true single sign-on to domain joined computers
  • Reduces usability issues by allowing users to use AD credentials to access all “Windows Intune" or “Office 365” services and not have to remember two identities and two passwords
  • Allows administrators the ability to enforce the organization’s password policies and account restrictions in both the on-premises and cloud-based organizations
  • Increases security of AD credentials since passwords are never synced to the cloud, all authentication happens on-premises
  • Reduces overall administration time and costs associated due to the above points

Based on a lot of TechNet articles , this was my design :

image

 

  • Will feature two ADFS farm servers (For redundancy reasons)
  • Will have two ADFS proxy servers (For redundancy reasons)
  • Will have one DirSync server (separate VM for preformance)
  • Will use a HW load balancer (Cisco , F5 , Citrix Netscaler) instead of Microsoft multicast NLB ( It doesn’t really work that well – or call it bad experiences) on both ADFS farm and ADFS proxy servers
  • Due to the size of the environment (Less than 50,000), WID (Windows Internal Database) server will have to be used
  • This WID SQL server will be running SQL Express edition.

In addition, we need to determine a few things upfront, as it will speed up the installation work. My personal experience is that you really need one of the internal Network guys from the customer to make this happen. We as “configmgr” guy’s are not familiar on how a customers network is organized and who is responsible for what part of the network)

  • External IP address of the federation service (In my example 212.x.x.x)
  • DMZ IP address of the federation service (which will be assigned to NLB as a shared virtual IP address , in my example 192.168.x.20)
  • DMZ server dedicated IP addresses (In my example 192.168.x.1 and 192.168.x.2) , they also reside in workgroup (not domain joined)
  • Internal ADFS farm shared virtual IP address assigned to the ADFS farm NLB (in my example 10.x.x.20)
  • Internal ADFS server dedicated IP addresses (in my example 10.x.x.1 and 10.x.x.2)
  • Fully qualified DNS name of the federation service, or ADFS FQDN (in my example Federation.SCUG.be) 
  • Service accounts used for various purposes in the setup
  • Public SSL certificate to secure traffic associated with ADFS. Certificates used for server authentication and token signing. Try to order a *.<yourdomainname> certificate.This will make your life much easier. (in my example *.SCUG.be) 
  • Necessary firewall ports are open from the Internet to ADFS Proxy server (port 443)
  • Necessary firewall ports are open from ADFS Proxy server to internal ADFS server (port 443)
  • Necessary firewall ports are open from the Internet to Dirsync server and visa versa (port 443)

This brings us to the end of this post. In the next few posts, we’ll cover additional configuration and installation steps and bring this Windows Intune SSO / ADFS 2.1 infrastructure on Windows Server 2012 to a usable state.

Stay Tuned !

 

Hope it Helps ,

Kenny Buntinx

Enterprise Client MVP

Lenovo X1 not PXE booting in Configmgr 2012 SP1 ?

10:51 am in ConfigMgr 2012, ConfigMgr 2012 SP1, Deployment, lenovo, Operating System Deployment, OSD, SCCM 2012, SCCM 2012 SP1, windows 8 by Kenny Buntinx [MVP]

 

Customer does zero-touch Windows 8 deployments on all computers , but when I tried it on the Lenovo Carbon X1 with the USB Ethernet dongle (P/N: 0A36322 or 0B67708) that Lenovo sells , it didn’t work.

However PXE boot works and I get an IP to begin the WinPE x64 download but once we get in the WinPE 4.0 stack , the Ethernet lights turns off and the machine reboots.To troubleshoot, I pressed F8 to bring up the CMD and IPCONFIG /all doesn’t list the NIC. Strange .

What if PXE boot does not work at all ? You need to do this first :

  • In the BIOS, under STARTUP, change the UEFI/Legacy Boot to "Legacy Only"
  • In the BIOS, under RESTART, change the OS Optimized Defaults to "Disabled", then choose "Load Setup Defaults".

On Configmgr 2012 sp1 ,  I imported the x64 drivers both from Lenovo the Ethernet dongle and then redeployed the boot images but no luck each time.

So hold on a minute .. does that X1 only have USB 3 ports ? Yes it has .

Solution : Download the USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family here : https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21129 . Make sure you have version 1.0.8.251 as older versions do not work with WINPE 4.0 .

Import the drivers in ConfigMgr 2012 SP1 and add them to your boot image . Now it will work !

Note : Other systems that exhibit this same behavior are the ASUS Zenbook UX31, Apple MacBook Air plus and I expect most of the new Ultrabook form factor systems that only have USB 3.0 ports and no built-in ethernet port will have this same problem.

Hope it Helps ,

Kenny Buntinx

Enterprise Client Management MVP

CM12 SP1 Management Point will not install on Server 2012

9:19 am in ConfigMgr 2012, ConfigMgr 2012 SP1, MP, SCCM 2012, SCCM 2012 SP1, Server 2012 by Kenny Buntinx [MVP]

 

Hi,

I am using Windows Server 2012, SQL 2012 SP1 and SCCM 2012 sp1, and I have one Primary site with a remote site server that will host the DP and MP role.

I am trying to install the Management Point (using HTTP for client connections) but it fails.  did have the SCCM 2007 client install on this server due to a automatic build process with CM07 and that was the in the end the issue . The CM07 client left traces.

Looking throught the msisetup log which said a previous version was detected, I used ccmsetup /uninstall to remove the client (which gets rid of it from control panel), and then removed the MP, rebooted and tried to install the MP again. However, the MP still wouldn’t install.

mpmsi log as below:

[9:53:33] Failed to compile ‘D:\SMS_CCM\CcmExec_Global.mof’ (Phase: 3, Object: 5, Lines: 76 – 83, Error: 80041002)
[9:53:33] Compiled ‘D:\SMS_CCM\CCMVDI.mof’
[9:53:33] Compiled ‘D:\SMS_CCM\ccmauthmessagehook.mof’
[9:53:33] Compiled ‘D:\SMS_CCM\LocationServices.mof’
[9:53:33] Compiled ‘D:\SMS_CCM\NetworkConfig.mof’
[9:53:33] Failed to compile ‘D:\SMS_CCM\PolicyDefaults.mof’ (Phase: 3, Object: 4, Lines: 49 – 57, Error: 80041002)
[9:53:33] Compiled ‘D:\SMS_CCM\PolicyAgentEvents.mof’
[9:53:33] Failed to compile ‘D:\SMS_CCM\StateMsgSchema.mof’ (Phase: 3, Object: 6, Lines: 89 – 94, Error: 80041002)
[9:53:33] Failed to compile ‘D:\SMS_CCM\DataTransferService.mof’ (Phase: 3, Object: 5, Lines: 318 – 323, Error: 80041002)
[9:53:33] Compiled ‘D:\SMS_CCM\CcmExec_MPFramework.mof’
[9:53:33] Compiled ‘D:\SMS_CCM\SmsCommon.mof’
[9:53:33] Compiled ‘D:\SMS_CCM\XmlStore.mof’
[9:53:33] Compiled ‘D:\SMS_CCM\InventoryAgentEvents.mof’
[9:53:33] Compiled ‘D:\SMS_CCM\SWMtrEvents.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\SWDistEvents.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\SrcUpdateEvents.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\PatchMgmtEvents.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\SMSNapEvents.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\MpStatusForwarderDefaults.mof’
[9:53:34] Failed to compile ‘D:\SMS_CCM\CcmExec_MP.mof’ (Phase: 3, Object: 1, Lines: 31 – 36, Error: 80041002)
[9:53:34] Compiled ‘D:\SMS_CCM\mp_pss.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\mp_ccmConfig.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\mp_ccmConfig_Defaults.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\MpEvents.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\OSDEventClasses.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\DPStatus.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\ImgDeployEvents.mof’
[9:53:34] Compiled ‘D:\SMS_CCM\DCMClientEvents.mof’
[9:53:35] Compiled ‘D:\SMS_CCM\SUMEvents.mof’
[9:53:35] Compiled ‘D:\SMS_CCM\OOBMgmtEvents.mof’
[9:53:35] Compiled ‘D:\SMS_CCM\PwrEvents.mof’
[9:53:35] @@ERR:25140
MSI (s) (8C!1C) [09:53:35:212]: Product: ConfigMgr Management Point — Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
CustomAction CcmRegisterWmiMofFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (8C:70) [09:53:35:241]: Note: 1: 2265 2:  3: -2147287035
MSI (s) (8C:70) [09:53:35:248]: User policy value ‘DisableRollback’ is 0
MSI (s) (8C:70) [09:53:35:248]: Machine policy value ‘DisableRollback’ is 0
Action ended 09:53:35: InstallFinalize. Return value 3.

MPsetup.log is below:

<01/17/13 09:52:54> SMSMP Setup Started….
<01/17/13 09:52:54> Parameters: D:\SCCM\bin\x64\rolesetup.exe /install /siteserver:SCCM01 SMSMP 0
<01/17/13 09:52:54> Installing Pre Reqs for SMSMP
<01/17/13 09:52:54>         ======== Installing Pre Reqs for Role SMSMP ========
<01/17/13 09:52:54> Found 2 Pre Reqs for Role SMSMP
<01/17/13 09:52:54> Pre Req MSXML60 found.
<01/17/13 09:52:54> No versions of MSXML60 are installed.  Would install new MSXML60.
<01/17/13 09:52:54> Enabling MSI logging.  msxml6_x64.msi will log to D:\SCCM\logs\msxml6_x64MSI.log
<01/17/13 09:52:54> Installing D:\SCCM\bin\x64\00000409\msxml6_x64.msi
<01/17/13 09:52:54> msxml6_x64.msi exited with return code: 0
<01/17/13 09:52:54> msxml6_x64.msi Installation was successful.
<01/17/13 09:52:54> Pre Req SqlNativeClient found.
<01/17/13 09:52:54> SqlNativeClient already installed (Product Code: {D9DDE0F8-0CFD-4C0F-8A07-C815DE47FF4D}). Would not install again.
<01/17/13 09:52:55> Pre Req SqlNativeClient is already installed. Skipping it.
<01/17/13 09:52:55>         ======== Completed Installation of Pre Reqs for Role SMSMP ========
<01/17/13 09:52:55> Installing the SMSMP
<01/17/13 09:52:55> Passed OS version check.
<01/17/13 09:52:55> IIS Service is installed.
<01/17/13 09:52:55> No versions of SMSMP are installed.  Installing new SMSMP.
<01/17/13 09:52:55> Enabling MSI logging.  mp.msi will log to D:\SCCM\logs\mpMSI.log
<01/17/13 09:52:55> Installing D:\SCCM\bin\x64\mp.msi CCMINSTALLDIR="D:\SMS_CCM" CCMSERVERDATAROOT="D:\SCCM" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=63 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<01/17/13 09:55:52> mp.msi exited with return code: 1603
<01/17/13 09:55:52> Backing up D:\SCCM\logs\mpMSI.log to D:\SCCM\logs\mpMSI.log.LastError
<01/17/13 09:55:52> Fatal MSI Error – mp.msi could not be installed.
<01/17/13 09:55:52> ~RoleSetup().
<01/17/13 09:59:03> ====================================================================

Solution :

I ran ccmclean, didn’t work for me initially. But this did the trick …

In an elevated Powershell window, run this:

Get-WMIObject -namespace “root” -query “SELECT * FROM __Namespace where name = ‘ccm’” | remove-wmiobject

It removes any last trace of ‘CCM’ from WMI. In my case I’d already uninstalled an old client and scoured the machine for any file or registry traces of ccm, but finally this worked.

Hope it helps ,

Kenny Buntinx

Citrix Provisioning Services and Microsoft System Center Configuration Manager 2012 SP1

12:54 pm in App-V, App-V 5.0, ConfigMgr 2012, ConfigMgr 2012 SP1, ConfigMgr V.next, MP, PVS, SCCM 2012 SP1, XEN, Xenapp, Xendestop, XENSERVER by Kenny Buntinx [MVP]

 

Hi ,

Today colleague Frank Vandenbergh at my customer responsible for Citrix was fighting to get there Citrix Provisioning services up and running with clients registering into System center Configuration Manager 2012 SP1. He has written already a blog post about it here , but I want to share some background info with you and dig a little deeper.

We had tried this in ConfigMgr 2007 out of the box without great succes resulting in a blog post :”ConfigMgr on xendesktop with the usage of provisioning server : Unique GUID issue and the smscfg.inihttp://scug.be/sccm/2011/02/04/configmgr-on-xendesktop-with-the-usage-of-provisioning-server-unique-guid-issue-and-the-smscfg-ini/

A little background :

Managing Virtual Desktops Created with PVS

 

Citrix Provisioning Services allows for multiple servers to stream their boot disk from the same master image (vDisk). During the boot process, PVS will make sure each server has a unique SID and dynamically apply the computername together with some other tasks to make those systems unique.

If you tried installing the SCCM client on a PVS image, you will notice that SCCM shows new machines with the same name every time a PVS target device reboots in standard mode. This is because the SCCM client changes the GUID when an image is pushed to new hardware. ConfigMgr uses the GUID to keep track inside his database.

ConfigMgr uses an ID that is generated on the Client to identify a machine inside the ConfigMgr hierarchy. This ID, also known as SMS GUID is generated during ConfigMgr Client installation.
An Algorithm, which combines the Timestamp (Time of ConfigMgr Client Installation) and the Universally Unique Identifier (UUID) is used to generate a unique Identifier.
A Client generates a new SMS GUID if the following things change

  • the SMBIOS serial number
  • the Machine SID
  • the Hardware ID (see appendix)

When VM is provisioned for the first time, the client will create a new GUID to register with server. If this client was discovered earlier by AD system discovery it can merge based on machine SID if previous history is present in SCCM site server DB. If server finds a match for this GUID in system_disc with exact AD machine account, the GUID and resource ID assigned will be same. If server finds a match based on AD machine SID in SID0, server will assign the GUID associated with the AD machine account and resource ID assigned will be the record that is the AD machine account. If it cannot find previous history using either of these methods, the server will assign the client passed in GUID and a new resource ID will be assigned.

Once new GUID is established for the VM, it will retain the same GUID for that VM based on machine SID as well as identity information restored locally on client from VDI persistent store. From the logs the client starts with GUID:78F1CF6F-814B-4E44-A2AE-729FB2C4F725 for reregistration that was established earlier and if cert changes it will associate the new cert with the GUID in re-registration. For any identity changes, client will retain the same GUID and same resource ID.

If resource ID changes (ItemKey in system_disc), it means there is no match in previous history for either client GUID or AD machine SID or client cert.

The heartbeat DDR will be sent when VM is provisioned for the first time i.e. when new ID is created. Thereafter it will depend on heartbeat discovery schedule set in the policy. Once DDR is sent by the client and gets processed by MP and site server, you should see all attributes in Admin console.

To ensure any desktops created with Provisioning Services operate correctly with ConfigMgr 2012, you must set the write cache to the target device’s hard drive. Using the Provisioning Services Console, in vDisk Properties, select Cache on device hard drive as the Cache Type. If you do not configure the cache this way, data required by ConfigMgr 2012 is not persisted when the desktops are restarted, which may result in unexpected behavior such as duplicate GUID’s or invalid inventory etc.

Unique Machine IDs for Shared Image Desktops

Virtual desktops built on the shared image provisioning solutions provided by XenDesktop (Provisioning Services and Machine Creation Services) presented a bit of a challenge for Configuration Manager 2007. 

With XenDesktop 5.6 and Configuration Manager 2012 / SP1 that problem is now history.  When you create your master image with either MCS or PVS simply install the SCCM agent and forget about it.  When you create cloned/streamed machines from that master image, the SCCM agent will automatically generate and store machine IDs that persist for the life of the VM.  Your virtual desktops will register and behave exactly like their physical counterparts.  One record per machine and that machine will continue to use the same ID across reboots.  This capability will also be available for XenApp servers streamed with Provisioning Services 6.1.

However it is not that simple …

Step 1 : Extending ConfigMgr Inventory for XenDesktop

XenDesktop makes available to ConfigMgr 2012 so that virtual desktops can be managed using this tool. The properties are available for the Citrix_virtualDesktopInfo class in the Root\Citrix\DesktopInformation namespace. See official info here : http://support.citrix.com/proddocs/topic/xendesktop-ibi/cds-manage-sccm-ibi.html

The following properties are available. Property names are those used in the Windows Management Instrumentation (WMI) provider:

  • BrokerSiteName – The name of your XenDesktop site; returns the same value as HostIdentifier
  • DesktopCatalogName – The name of the catalog associated with the desktop
  • DesktopGroupName – The name of the desktop group associated with the desktop
  • HostIdentifier – The name of your XenDesktop site; returns the same value as BrokerSiteName
  • IsAssigned – False for a pooled-random desktop, otherwise true
  • IsVirtualMachine – True for a virtual machine, false for a physical machine
  • OSChangesPersist – False if the desktop operating system image is reset to a clean state every time it is restarted, otherwise true
  • PersistentDataLocation – The location where Configuration Manager stores persistent data. This is not accessible to users.
  • PersonalvDiskDriveLetter – For a desktop with a personal vDisk, the drive letter you assign to the personal vDisk

The properties BrokerSiteName, DesktopCatalogName, DesktopGroupName, and HostIdentifier are determined when the desktop registers with the controller, so they are null for a desktop that has not fully registered.

You can display the properties using the hardware inventory in Configuration Manager or using attributes of Configuration Manager objects. When you do, the names may include spaces or vary slightly in other ways.

On how to extend the HW inventory , Marius Sandbu has written an excellent acticle about that here : https://msandbu.wordpress.com/2013/03/27/excalibur-and-configuration-manager/

Step 2 : Create your Master VM with care !

 

Keep in mind that your Master VM is a fully configured and running VM. You allow SCCM to install the client as normal and so the SCCM server is aware of the machine so I guess you can say the reverse it true as well. You do this install before you do create the catalog from the VM image of course. From there it should just work.

  • Install the Configuration Manager client software on the golden image as part of your automated Configmgr Task Sequence
  • Stop the SMS Agent Host service (CCMExec.exe) on the reference computer (net stop ccmexec).
  • Delete the C:\Windows\SMSCFG.INI file
  • Delete the current certificates in the "SMS" certificate store. ( open an MMC.exe)
  • Change the provisioning image from private to standard.
  • Stream the vdisk to target computers.

If you do not remove the certificates , you will get into the following problem that registration of the client will not succeed successfully. What will happen is :

1. System booting up in “private mode”, the master image. Hostname is TEST1.

2. Same disk is now booted in standard “readonly” mode. Hostname is TEST1. SCCM is correctly getting the persistent disk location from WMI . SCCM restores everything from CCMCFG.BAK, except the correct SMBIOS value. It reports SID unchanged, HWID unchanged, SMBIOS changed (it is still reading the SMBIOS value from the ‘master’ device in the SMSCFG.INI file in the default location.)

3. ClientIDManagerStartup reports: Detected hardware identity change, generating new certificates.The Client is re-registering with the SCCM server.

4. The SCCM service seems to be restarted following the registration witch is normal .The ccmexec service restart is expected even on non-VDI systems if any of the policy configuration require service to be restarted. The heartbeat DDR will be sent when VM is provisioned for the first time i.e. when new ID is created.

5. In the SCCM console the record is recreated and as a result we loose the software metering information / direct collection memberships. We did the test with removing the SMSCFG.ini file in the “master” disk. On next startup SCCM is reading everything correctly from the CCMCFG.BAK and reports “SMBIOS unchanged”.

6.The computer object is not recreated, but we have a feeling the client is still not registered correctly because the console is not updating its last hardbeat time etc.  .This is due the faulty SMS Client certificates being stuck in the “Master Images” . Remove the Certificates as said before and you’ll be fine .

 

Hope it Helps ,

Kenny Buntinx

Configmgr 2012 RTM/SP1 and Riverbed Appliances not a good marriage: “Application fails during OSD Task sequence with exit code 16389 (RequestContent from CAS failed. Error = 0x87d01202)” and “Apply driver Package does not apply the NIC driver”

3:12 pm in ConfigMgr 2012, ConfigMgr 2012 SP1, OSD, riverbed, sccm, SCCM 2012, SCCM 2012 SP1, sccm RTM by Kenny Buntinx [MVP]

 

Environment : SCCM2012 SP1 (W2K8 R2 sp1) and the SQL2K8 R2 SP2 that is hosting the database is running on a separate VM. Our source files are stored on a CIFS share.

We experienced a strange behavior when using a task sequence to deploy an OS together with .Net framework (4.5) application after the upgrade to SP1 and our OSD task sequence wouldn’t apply any driver anymore. This looked suspicious , but finally it had nothing to do with the upgrade to sp1 , but with riverbed appliances for WAN traffic optimization.

For the driver packages, the data source folder is created successfully and contains all the subfolders (i.e.0EC7ACC5-0776-4676-B90B-967D7769C185) with the driver files. The problem is that when we distribute the content to our DP’s, it indicates everything is successfully distributed on all DP’s, but when our OSD wants to use those drivers package it says no files found.

Problem 1 : The application wouldn’t install anymore and fail .

Once that the step kicks in to install the application we get the following error:

"The task sequence failed to install application Microsoft .NET Framework 4.5(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6) for action (Install Application .NET) in the group () with exit code 16389."

Extract from CITaskMgr.log
Initiating task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2 (WKS_CORP_.NET Framework 4.5_EN_64) for target: , consumer: {B351446F-8FDF-4DD9-AE75-F9E818E79D25}    CITaskMgr    1/29/2013 5:53:51 PM    1036 (0x040C)
Initiating content download : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload)    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
RequestContent from CAS failed. Error = 0x87d01202    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
Binary content download failed. Error = 0x87d01202 : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload)    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
State transition to (Failure), Error(0x87d01202) : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload)    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
State transition to (Failure), Param(-2016407038) : CTaskConsumer(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2.{4FFAD6D2-6F40-4870-96F5-B49B091CA9D2})    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
ResumeTask failed. Error = 0x87d01202 : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload)    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
CCITaskMgr::InitiateTask failed. Error =0x87d01202    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
Release task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2 for target: , consumer {B351446F-8FDF-4DD9-AE75-F9E818E79D25}    CITaskMgr    1/29/2013 5:53:53 PM    1036 (0x040C)
Release task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6.2 for target: , consumer {EE171CEB-C12F-47FD-8564-57CB90B02641}    CITaskMgr    1/29/2013 5:53:53 PM    1036 (0x040C)
Release task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6.2 for target: , consumer {544D045C-A3DE-4B93-8C8C-B68B0DE703B6}    CITaskMgr    1/29/2013 5:53:53 PM    1036 (0x040C)

Extract from SMSTS.log
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
Passed in version 2 for ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6.2 = DownloadFailed    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
NotifyProgress received: 24 (Application download failed )    InstallApplication    1/29/2013 5:53:53 PM    2120 (0x0848)
GetAppMgmtSDKInterface successful    InstallApplication    1/29/2013 5:53:53 PM    2120 (0x0848)
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
Passed in version 2 for ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6.2 = DownloadFailed    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
GetAppMgmtSDKInterface successful    InstallApplication    1/29/2013 5:53:53 PM    2120 (0x0848)
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)

Extract from CIDownloader.log
CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task    CIDownloader    1/29/2013 5:53:51 PM    1036 (0x040C)
CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task    CIDownloader    1/29/2013 5:53:53 PM    2036 (0x07F4)
VerifyCIDocumentHash – Preparing to verify hash for CI document ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6/2/MANIFEST    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
VerifyCIDocumentHash – Preparing to verify hash for CI document ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6/2/PROPERTIES    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
GetInstanceFromLantern failed (0x80041002).    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
DCM::LanternUtils::CheckCIExists – Wmi Instance: PolicyPlatform_Policy.Name="ScopeId_59BCBA4C_DFF4_4108_922A_B0F379D9AC3A_Application_0e53477f_e752_4d52_b9b2_db24e27961b6_Platform_PolicyDocument",Authority="System Center Configuration Manager",Revision=2 not found in namespace: root\microsoft\policyplatform\Documents\Local. CI not found.    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
VerifyCIDocumentHash – Preparing to verify hash for CI document ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e/2/MANIFEST    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
VerifyCIDocumentHash – Preparing to verify hash for CI document ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e/2/PROPERTIES    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
GetInstanceFromLantern failed (0x80041002).    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
DCM::LanternUtils::CheckCIExists – Wmi Instance: PolicyPlatform_Policy.Name="ScopeId_59BCBA4C_DFF4_4108_922A_B0F379D9AC3A_DeploymentType_ad388e96_a3ce_4fc8_9c56_75d3dc5c116e_Discovery_PolicyDocument",Authority="System Center Configuration Manager",Revision=2 not found in namespace: root\microsoft\policyplatform\Documents\Local. CI not found.    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)

Problem 2 : The apply driver package did not apply any driver :

In fact, ALL the other driver packages we have made till now have the same settings, but those have well a size between 80 – 600 MB.

The distmgr.log (the driver package with 0 size is EUA00060)

Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:49:06 AM    3268 (0x0CC4)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:44 AM    3476 (0x0D94)
Found package properties updated notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:49 AM    3268 (0x0CC4)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:49 AM    3476 (0x0D94)
Found notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:54 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:54 AM    3268 (0x0CC4)
Starting package processing thread, thread ID = 0x1204 (4612)    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    3268 (0x0CC4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4612 GMTDATE=Mon Jan 28 08:57:55.383 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Start adding package EUA00060…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
The Package Action is 2, the Update Mask is 0 and UpdateMaskEx is 0.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2300    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Taking package snapshot for package EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
The content package does not contain any contents.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2376    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Adding these contents to the package EUA00060 version 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Successfully created/updated the package EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4612 GMTDATE=Mon Jan 28 08:57:55.554 2013 ISTR0="EUA00060" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Created policy provider trigger for ID EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Package EUA00060 does not have a preferred sender.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
A program for package EUA00060 has been added or removed, therefore it needs to be replicated to all child sites.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Package EUA00060 is new or has changed, replicating to all applicable sites.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2301    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
StoredPkgVersion (1) of package EUA00060. StoredPkgVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
SourceVersion (1) of package EUA00060. SourceVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Adding these contents to the package EUA00060 version 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4612 GMTDATE=Mon Jan 28 08:57:56.760 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Exiting package processing thread.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:59 AM    3476 (0x0D94)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:00 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:00 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:05 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:05 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:10 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:10 AM    3268 (0x0CC4)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:14 AM    3476 (0x0D94)
Found package properties updated notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:19 AM    3268 (0x0CC4)
Found notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:24 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:24 AM    3268 (0x0CC4)
Starting package processing thread, thread ID = 0xA68 (2664)    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    3268 (0x0CC4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2664 GMTDATE=Mon Jan 28 09:01:25.352 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Start updating the package EUA00060…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
The Package Action is 1, the Update Mask is 18 and UpdateMaskEx is 0.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Successfully created/updated the package EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2664 GMTDATE=Mon Jan 28 09:01:25.425 2013 ISTR0="EUA00060" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Set share security on share \\TGDAMSA01.tgtest.com\SCCMContentLib$    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Created policy provider trigger for ID EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Package EUA00060 does not have a preferred sender.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Package EUA00060 is new or has changed, replicating to all applicable sites.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2301    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
StoredPkgVersion (1) of package EUA00060. StoredPkgVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
SourceVersion (1) of package EUA00060. SourceVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2664 GMTDATE=Mon Jan 28 09:01:26.028 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:26 AM    2664 (0x0A68)
Exiting package processing thread.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:26 AM    2664 (0x0A68)
Found package properties updated notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:02:59 AM    3268 (0x0CC4)
Found notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:04 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:04 AM    3268 (0x0CC4)
Starting package processing thread, thread ID = 0x1248 (4680)    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    3268 (0x0CC4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4680 GMTDATE=Mon Jan 28 09:03:05.353 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Start updating the package EUA00060…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
The Package Action is 1, the Update Mask is 264192 and UpdateMaskEx is 0.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Successfully created/updated the package EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4680 GMTDATE=Mon Jan 28 09:03:05.420 2013 ISTR0="EUA00060" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Set share security on share \\TGDAMSA01.tgtest.com\SCCMContentLib$    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Created policy provider trigger for ID EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Package EUA00060 does not have a preferred sender.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Package EUA00060 is new or has changed, replicating to all applicable sites.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2301    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
StoredPkgVersion (1) of package EUA00060. StoredPkgVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
SourceVersion (1) of package EUA00060. SourceVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4680 GMTDATE=Mon Jan 28 09:03:06.014 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:06 AM    4680 (0x1248)
Exiting package processing thread.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:06 AM    4680 (0x1248)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:09 AM    3476 (0x0D94)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:10 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:10 AM    3268 (0x0CC4)
Found notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    3268 (0x0CC4)
Starting package processing thread, thread ID = 0x99C (2460)    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    3268 (0x0CC4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2460 GMTDATE=Mon Jan 28 09:03:20.901 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    2460 (0x099C)
No action specified for the package EUA00060.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    2460 (0x099C)
Start adding package to server ["Display=\\TGDAMSA03.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\TGDAMSA03.tgtest.com\…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2460 (0x099C)
Attempting to add or update a package on a distribution point.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2760 (0x0AC8)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2760 GMTDATE=Mon Jan 28 09:03:21.473 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="["Display=\\TGDAMSA03.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\TGDAMSA03.tgtest.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="EUA00060" AID1=404 AVAL1="["Display=\\TGDAMSA03.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\TGDAMSA03.tgtest.com\"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2760 (0x0AC8)
Start adding package to server ["Display=\\BEBRMSA02V.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA02V.tgtest.com\…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2460 (0x099C)
Attempting to add or update a package on a distribution point.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    5004 (0x138C)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=5004 GMTDATE=Mon Jan 28 09:03:21.986 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="["Display=\\BEBRMSA02V.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA02V.tgtest.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="EUA00060" AID1=404 AVAL1="["Display=\\BEBRMSA02V.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA02V.tgtest.com\"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    5004 (0x138C)
The current user context will be used for connecting to ["Display=\\TGDAMSA03.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\TGDAMSA03.tgtest.com\.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2760 (0x0AC8)
Successfully made a network connection to \\TGDAMSA03.tgtest.com\ADMIN$.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2760 (0x0AC8)
CreateSignatureShare, connecting to DP    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
Signature share exists on distribution point path \\TGDAMSA03.tgtest.com\SMSSIG$    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
Set share security on share \\TGDAMSA03.tgtest.com\SMSSIG$    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
Ignoring drive \\TGDAMSA03.tgtest.com\C$\.  File \\TGDAMSA03.tgtest.com\C$\NO_SMS_ON_DRIVE.SMS exists.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine (TGDAMSA01.tgtest.com) is submitting SDK changes from site(EUA)    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
Start adding package to server ["Display=\\BEBRMSA01.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA01.tgtest.com\…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2460 (0x099C)
Will wait for 3 threads to end.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2460 (0x099C)
Thread Handle = 0000000000001F04    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2460 (0x099C)
Attempting to add or update a package on a distribution point.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    540 (0x021C)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=540 GMTDATE=Mon Jan 28 09:03:22.488 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="["Display=\\BEBRMSA01.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA01.tgtest.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="EUA00060" AID1=404 AVAL1="["Display=\\BEBRMSA01.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA01.tgtest.

Solution :

After further investigations and testing, we found the source of our problems: Riverbed Appliances at  www.riverbed.com !

In there infrastructure, there are RIVERBED appliances between our Datacenter (where the CIFS is located) and remote locations (where DP’s resides) and after we bypass the traffic optimization for the IP’s concerned (CIFS + SCCM servers), a simple "Update Content" on affected packages results immediately in a (re-)provisionning of the content library on the DP’s.

This wasn’t a Configmgr SP1 related issue , but keep in mind when you implement WAN optimization solutions after you have implemented your configmgr 2012 environment.

I have investigated with Vincent Devos (enigineer from the company) . In the meantime we where out of ideas and therefore posted the 2 original forum questions to get additional help . You will find them here :

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/b5373b31-e594-4e1b-b6b9-ffecea05531e

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/a19a37ce-ffa5-41eb-b6f7-dba6f50894dc?prof=required

Hope it Helps ,

Kenny Buntinx

System Center Configuration Manager MVP

Configmgr 2012 SP1 : PowerShell Script to repair “Broken Applications after upgrading them from RTM”

7:52 pm in Application Model, applications, CM12, ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, Deployment, deployment types, SCCM 2012, SCCM 2012 SP1, upgrade by Kenny Buntinx [MVP]

 

Upgrading a Configmgr 2012 RTM environment to a new SP1 environment . After the upgrade was successfully performed , suddenly all applications within my OSD task sequence start failing as described in my previous blog post here : http://scug.be/sccm/2013/01/08/configmgr-2012-sp1-broken-applications-after-upgrading-from-rtm/

Finally we have found some other errors as well , they are listed here :

  • The task sequence failed to install application Intel Management Engine 6.0.40.1215(ScopeId_67A221E3-64F0-47D4-AA5A-BB3729EC221F/Application_2071f753-7604-42a5-b6be-b1b45c3c1f0a) for action (Install HW Driver Applications for HP8540P) in the group () with exit code 615. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
  • The task sequence failed to install application NVIDIA Quadro/NVS Mobile Drivers 305.93(ScopeId_67A221E3-64F0-47D4-AA5A-BB3729EC221F/Application_17e0153e-3d4f-467b-a2b3-68491516b0e1) for action (Install HW Driver Applications for HP8540P) in the group () with exit code 580. The operating system reported error 580: An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread.
  • The task sequence failed to install application Synaptics Touch Pad Driver(ScopeId_67A221E3-64F0-47D4-AA5A-BB3729EC221F/Application_a0628bfc-3f06-4096-a001-c1a6c92675ea) for action (Install HW Driver Applications for HP8540P) in the group () with exit code 16389. The operating system reported error 2: The system cannot find the file specified.

We found a workaround, you have simply to add a comment to each DT and it will update the content ID. Nevertheless, the change means that a redistribution of your application on all your DP’s.

BUT , that is all manual work , and we hate that , don’t we Smile with tongue out . Luckily we have an excellent PowerShell scripter in our team and all credits for creating this script goes to  Bart Serneels. He has written a PowerShell script to do all the work . He was happy to share this with you guys.

Here is the script : (replace VVM with your “Site Code” )

 

What the script will do is :

  1. Look for any application that has no deployment attached to it
  2. Opens the application deployment type(s) and looks for a description .
  3. If the description field is empty , it will update that field with the deployment type name.
  4. If the description field exists , it will make a backup , adapt it with the deployment type name , save it , reopen and revert to the backup descriptions and save it once more .

Again  , this is a workaround that helped us fixing our issues and no guarantee it will work for you .

Hope it Helps ,

Kenny Buntinx

MVP ConfigMgr

ConfigMgr 2012 SP1 : The 8dot3name settings are disabled on the volumes upon partitioning and formatting of the local disk.

8:59 am in adk, ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, OSD, sccm, SCCM 2012, SCCM 2012 SP1, sccm RTM, WAIK by Kenny Buntinx [MVP]

 

Ever since we’ve been capturing our images with ConfigMgr 2012 SP1 we’ve noticed that 8dot3name creation is disabled on all volumes on the hard drive on the volume level when installing a machine with the same installation source as before (Windows 7 Enterprise SP1 x64). In our environment, we need this to be enabled for certain applications to work properly. ( Almost all Legacy XP Apps that work on Win7) . Nowhere is this change documented .

This wasn’t the case with ConfigMgr 2012 RTM , the difference there was that we where using WAIK instead of ADK.

I’ve been in discussions with the System Center Configuration Manager product team and received a response from them late yesterday.  They did, in fact, change the default behavior of the formatting tools in Windows 8. (ADK) 

They are working with them (ADK Team)  to figure out where/how this change was communicated, and to see how they can best communicate it more broadly.  In the meantime, They’ll continue working with them to figure out what our options are for resolving/working around this issue in Configmgr 2012 SP1.

Workarounds :

One option would be to create your own partitioning and formatting script and use that as a Run Command Line action instead of using there built-in Format and Partition Disk action.  I know that’s not elegant, but may be your best bet for now.

Here’s what the Windows imaging team had to say (with some additions/clarifications from me)…

Windows 8 does have 8.3 disabled on non-OS drives by default.  ImageX (and other Windows imaging tools) does preserve the same when capturing the image, and will apply as how the image was captured.  In the case where files with short file names are in a captured image, but the volume where the image will be applied has 8.3 disabled, WIMGAPI will enable 8.3 on the volume and set the short file names accordingly when the image is applied.

If they formatted a data volume using a Windows 8 format utility, short names would be disabled by default on the volume.  This is the default way format behaves.

How short names get enabled on the system volume is that setup explicitly turns them back on after formatting the system volume.  (i.e. if you’re applying an image and not running Setup, they won’t be turned back on automatically)

They can override this on the format command line with the following switch:  format x: /s:enable (where x: is the drive letter to format)  Unfortunately, you can’t add your own command line switches when using our built-in Format and Partition Disk action.

To manually enable 8.3 naming after formatting, you can use fsutil.exe from the command line:

                fsutil 8dot3name set x: 0 (where x: is the drive letter to enable 8.3 naming on)

This will enable short names on the given volume and it takes effect immediately.  (and yes, 0 does enable short names).  Unfortunately, fsutil.exe is not included in Windows PE, so you would have to copy it over to your boot media and run it with a Run Command Line action.

Hope it Helps,

Kenny Buntinx

MVP System Center Configuration Manager

How to create an application for deploying the App-V 5.0 Client with Configmgr 2012

9:09 pm in App-V, App-V 5.0, Application Model, AppV, CM12, ConfigMgr 2012 SP1, Deployment, deployment types, detection methods, Operating System Deployment, OSD, sccm, SCCM 2012 SP1, vbscript by Kenny Buntinx [MVP]

 

In this blog post we will show you how to create the application for deploying the App-V 5.0 client which is part of the MDOP ( Microsoft Desktop Optimization Pack )suite.

App-V 5.0 client is supported on the following platforms (As you can see , there is NO XP support) :

image

First we need to have a look on the exact prerequisites needed to run the App-V 5.0 client . You will find that kind of information here : http://technet.microsoft.com/en-us/library/jj713458.aspx

However the information on what version you need on the Microsoft Visual C++ is vague. We will clarify that below :

  1. Microsoft Windows .NET Framework 4 (Full Package) (http://www.microsoft.com/en-us/download/details.aspx?id=17718)
  2. Windows PowerShell 3.0 (http://www.microsoft.com/en-us/download/details.aspx?id=34595)
  3. Download and install KB2533623 (http://www.microsoft.com/en-us/download/details.aspx?id=26746)
  4. The Microsoft Visual C++ 2010 SP1 x64 Redistributable –> v10.0.40219 (http://go.microsoft.com/fwlink/?LinkId=268896)

image

  1. The Microsoft Visual C++ 2005 SP1 x86 Redistributable –> v8.0.61001 http://www.microsoft.com/en-us/download/details.aspx?id=26347

image

Now we need to create for each component an application . Lets start :

Windows .NET Framework 4 (Full Package)

Knipsel

Knipsel2

Knipsel3

Full installation code : dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT

Knipsel4

Create 2 detection methods as shown below

Knipsel5

Detection Method 1 : {8E34682C-8118-31F1-BC4C-98CD9675E1C2}

Knipsel6

Detection Method 2 : {F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}

Windows PowerShell 3.0

31

Full installation code : c:\windows\System32\wusa.exe "Windows6.1-KB2506143-x64.msu" /quiet /norestart

32

Use a script as detection method :

33

Full detection script :

KB2533623 –> Apply hotfix in your base image or use CBS updates with offline updates

Microsoft Visual C++ 2010 SP1 –> Use download link specified above and use MSI detection methods

Microsoft Visual C++ 2005 SP1 –> Use download link specified above and use MSI detection methods

App-V 5.0 Client itself

When done , we going to create the App-V 5.0 Client Application . Deploy one of the following Windows Installer files to the target computer. The Windows Installer file you specify must match the configuration of the target computer.

  • If the target computer is running a 32-bit Microsoft Windows operating system, deploy the appv_client_MSI_x86.msi.
  • If the target computer is running a 64-bit Microsoft Windows operating system, deploy the appv_client_MSI_x64.msi.
  • If you are deploying the App-V 5.0 Remote Desktop Services client, deploy the appv_client_rds_MSI_x64.msi.

14

Create your application.

10

Create 2 deployment types : x64 and x86

11

For the X64 deployment type

13

Use the regular msi install parameters

15

Use the regular msi detection method

16

Now you must create dependencies . Make sure you select AUTO Install !

17

First create the Visual C++ 2005 SP1 x86 and select the deployment type you created earlier .

18

Then create a WMF 3.0 one and select the deployment type you created earlier .

19

Then create the Visual C++ 2010 SP1 x86 and select the deployment type you created earlier .

20

Then as the last one , create the Visual C++ 2010 SP1 x64 and select the deployment type you created earlier .

21

 

Your al set , your App-V 5.0 install is ready to be used .

Hope it Helps ,

Kenny Buntinx