Comments on: System Center Mobile Device Manager 2008 – Distributing Software – Part 2 http://mobilitydojo.net/2008/10/31/system-center-mobile-device-manager-2008-distributing-software-part-2/ place of the mobility way Wed, 08 Sep 2010 02:04:16 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Andreas http://mobilitydojo.net/2008/10/31/system-center-mobile-device-manager-2008-distributing-software-part-2/comment-page-1/#comment-7139 Andreas Wed, 18 Nov 2009 14:37:40 +0000 http://mobilitydojo.net/?p=364#comment-7139 The WSUS in SCMDM has shown itself to be a sneaky little component. Over at the TechNet forums there's a lot of reports that upgrading the WSUS to SP2 breaks things. Have you done any Windows Updates lately? Is the WSUS server installed on the DM server? (If I remember correctly there's some extra steps if you don't have them on the same server.) As for devices not receiving software there could be both server side and client side issues. (It seems you have a server side issue, so the question is if there's something with the device as well.) Does this apply to only a specific device model, or have you tried different models? It's also convenient to test with the device emulator as a reference model. The WSUS in SCMDM has shown itself to be a sneaky little component. Over at the TechNet forums there’s a lot of reports that upgrading the WSUS to SP2 breaks things. Have you done any Windows Updates lately?

Is the WSUS server installed on the DM server? (If I remember correctly there’s some extra steps if you don’t have them on the same server.)

As for devices not receiving software there could be both server side and client side issues. (It seems you have a server side issue, so the question is if there’s something with the device as well.) Does this apply to only a specific device model, or have you tried different models? It’s also convenient to test with the device emulator as a reference model.

]]> By: JohnV http://mobilitydojo.net/2008/10/31/system-center-mobile-device-manager-2008-distributing-software-part-2/comment-page-1/#comment-7112 JohnV Tue, 17 Nov 2009 11:13:16 +0000 http://mobilitydojo.net/?p=364#comment-7112 Hi, thanks for the posts - very useful. A few questions regarding software distribution:- a. When I approve the software package I see the same approval screens and then the package disappears from the Admin console. I can't find it in WSUS either and nothing is distributed to the device. b. My device reports as successfully enrolled but I cannot update device details, or distribute software. Any ideas? Hi, thanks for the posts – very useful.
A few questions regarding software distribution:-

a. When I approve the software package I see the same approval screens and then the package disappears from the Admin console. I can’t find it in WSUS either and nothing is distributed to the device.

b. My device reports as successfully enrolled but I cannot update device details, or distribute software.

Any ideas?

]]> By: Andreas http://mobilitydojo.net/2008/10/31/system-center-mobile-device-manager-2008-distributing-software-part-2/comment-page-1/#comment-1025 Andreas Sat, 14 Mar 2009 17:07:08 +0000 http://mobilitydojo.net/?p=364#comment-1025 The certificate of the CA needs to be in the root store, but this is done during the enrollment process in SCMDM so that's not something you need to do manually. For the SPC store you need to provision the certificate the cab file is signed with - which would normally be the one you issued via the Code Signing template. Hope that makes sense - there's a lot of certificates to keep track of with SCMDM :) The certificate of the CA needs to be in the root store, but this is done during the enrollment process in SCMDM so that’s not something you need to do manually. For the SPC store you need to provision the certificate the cab file is signed with – which would normally be the one you issued via the Code Signing template.

Hope that makes sense – there’s a lot of certificates to keep track of with SCMDM :)

]]> By: Deepak Kumar http://mobilitydojo.net/2008/10/31/system-center-mobile-device-manager-2008-distributing-software-part-2/comment-page-1/#comment-1024 Deepak Kumar Sat, 14 Mar 2009 12:18:22 +0000 http://mobilitydojo.net/?p=364#comment-1024 Hi Andreas, Nice post :-) One query. For Mobile Device which certificate we need to import in SPC/Privileged Execution Trust Authorities? Is it Certificate Authority Certificate or certificate issued via Code sign Template!! From your post it seems Codesign Template certificate. Thanks Hi Andreas,

Nice post :-)

One query. For Mobile Device which certificate we need to import in SPC/Privileged Execution Trust Authorities?

Is it Certificate Authority Certificate or certificate issued via Code sign Template!!

From your post it seems Codesign Template certificate.

Thanks

]]> By: Andreas http://mobilitydojo.net/2008/10/31/system-center-mobile-device-manager-2008-distributing-software-part-2/comment-page-1/#comment-120 Andreas Thu, 22 Jan 2009 23:35:05 +0000 http://mobilitydojo.net/?p=364#comment-120 Ideally you would prepare a code signing certificate when you initially deploy the servers so you will be prepared the day you want to start distributing software. Even if the application is already signed with a certificate issued by another CA than your own you can resign it with your own certificate and it would deploy without a hitch. On the first connect a device does to the DM Server policies will be calculated/pushed down before the software distribution process can perform any tasks. Now I cannot say for sure that's what happens on all subsequent connections. I'll have to dig through some documentation to see if I can locate the specifics. Initially I am guessing that these tasks can get out of synch with each other though, and that you risk having to wait another schedule run for the process to complete. But I'll look it up, and post another comment if/when I find something. Ideally you would prepare a code signing certificate when you initially deploy the servers so you will be prepared the day you want to start distributing software.

Even if the application is already signed with a certificate issued by another CA than your own you can resign it with your own certificate and it would deploy without a hitch.

On the first connect a device does to the DM Server policies will be calculated/pushed down before the software distribution process can perform any tasks.

Now I cannot say for sure that’s what happens on all subsequent connections. I’ll have to dig through some documentation to see if I can locate the specifics. Initially I am guessing that these tasks can get out of synch with each other though, and that you risk having to wait another schedule run for the process to complete.

But I’ll look it up, and post another comment if/when I find something.

]]> By: Centpro http://mobilitydojo.net/2008/10/31/system-center-mobile-device-manager-2008-distributing-software-part-2/comment-page-1/#comment-119 Centpro Thu, 22 Jan 2009 22:26:38 +0000 http://mobilitydojo.net/?p=364#comment-119 Excellent walk through. Thank you. Is there a decision tree published anywhere for the connection/policy/app install process? If I have something to get out in a hurry, but its signed with by a CA that I also have to deploy certs for, is it even possible that my Root cert/SPC/Priv Exec certs would be installed before the install is attempted? Where is there more on this? Thank you. Excellent walk through. Thank you.

Is there a decision tree published anywhere for the connection/policy/app install process?

If I have something to get out in a hurry, but its signed with by a CA that I also have to deploy certs for, is it even possible that my Root cert/SPC/Priv Exec certs would be installed before the install is attempted?

Where is there more on this?

Thank you.

]]> By: Andreas http://mobilitydojo.net/2008/10/31/system-center-mobile-device-manager-2008-distributing-software-part-2/comment-page-1/#comment-63 Andreas Sat, 08 Nov 2008 09:23:32 +0000 http://mobilitydojo.net/?p=364#comment-63 The device will always check for new apps when it connects. But new apps will only be installed after SCMDM has recalculated policies. This should coincide with the connection schedule if nothing is altered from it defaults. I think the default for recalculation is 8 hours. The default schedule is 8 hours. But this means that if you are testing devices, and use the "Connect Now" tool from the resource kit you may experience that nothing is distributed. When I tested for the purpose of this guide I set the recalculation policy to 30 minutes but for production purposes this might not work well. The device will always check for new apps when it connects. But new apps will only be installed after SCMDM has recalculated policies. This should coincide with the connection schedule if nothing is altered from it defaults. I think the default for recalculation is 8 hours. The default schedule is 8 hours. But this means that if you are testing devices, and use the “Connect Now” tool from the resource kit you may experience that nothing is distributed.
When I tested for the purpose of this guide I set the recalculation policy to 30 minutes but for production purposes this might not work well.

]]> By: D http://mobilitydojo.net/2008/10/31/system-center-mobile-device-manager-2008-distributing-software-part-2/comment-page-1/#comment-62 D Fri, 07 Nov 2008 23:44:32 +0000 http://mobilitydojo.net/?p=364#comment-62 Is there anyway to force it to check for new apps to install? What is the default interval check? Great writups. Is there anyway to force it to check for new apps to install? What is the default interval check?

Great writups.

]]>