SCCM Deployment Status not updating

[robyholmes]

Hi,

 

I'm very new to SSCM so please do excuse me if I'm being very thick. I've setup a deployment for the OneDrive All Users installer and tested it on a test machine. All went well and it installed fine. I then delete that deployment and created a new one to push it to all machines. However its been 24 hours now and the deployment status still hasn't changed since I first looked at it. I'm sure machines are installing the software fine but I just can't monitor it. The summarization is scheduled (At least that's what it tells me when I try and run it manually) and the date and time is updating.

 

I've checked SCCM for errors in the System Status area and did find one this morning but I've fixed that now and no errors are being shown. However I'm still seeing the first 'Update' of the status of the deployment.

 

Has anyone got any ideas of what to try next? Or what I'm doing wrong? I'm sure you'll need more information so I'll try and get you it as requested.

 

Thanks, Rob

[robyholmes]

Anyone? Any advice? It's still not updated but SCCM all seems happy. Lost as to what to look for next.

[hellgate24]

Have you set it as an available deployment rather than required?

 

An available deployment will sit in Unknown deployment state until a user initiates it themselves through software center. A required deployment will update deployment status by itself whenever the machine next runs its deployment evaluation cycle as defined in your client settings.

[robyholmes]

Have you set it as an available deployment rather than required?

 

An available deployment will sit in Unknown deployment state until a user initiates it themselves through software center. A required deployment will update deployment status by itself whenever the machine next runs its deployment evaluation cycle as defined in your client settings.

 

I've checked to be sure and it's marked as required. The status / summarization screen shows it installing on 3 machines, and some errors on others. However this information has been static since I first looked at it. One of the machine it says its 'In Progress' on I know has the software on it. So I'm pretty sure its installing on machines I just can't see an up to to date progress of it.

 

I've done some test deployments before and I've found the same thing each time. Normally this was just to one or two machines.

[Steve21]

Normally those kind of issues are related to the heartbeat settings for the clients

 

There’s tasks that’s scheduled to run to check things like software and normally they are set for once every 24 hours, meaning if the machine is off during that time etc it won’t report back

 

We tweaked all of these a lot to do scans every few hours or mid-day etc when we expected these to be on

 

If you have sccm right click tools installed you could force a manual update for the machine and see if it pulls the right stats through and then it’s likely related to that

 

Steve

[robyholmes]

Normally those kind of issues are related to the heartbeat settings for the clients

 

There’s tasks that’s scheduled to run to check things like software and normally they are set for once every 24 hours, meaning if the machine is off during that time etc it won’t report back

 

We tweaked all of these a lot to do scans every few hours or mid-day etc when we expected these to be on

 

If you have sccm right click tools installed you could force a manual update for the machine and see if it pulls the right stats through and then it’s likely related to that

 

Steve

 

I maybe could understand this if it hadn't been a few days but I pushed this deployment out on the 13th May. Do you know where these settings are configured just so I can check what ours is set too?

[Steve21]

But even after a month it it’s never on during that scan (let’s say 6pm) it’ll never update, as it didn’t just run it when it’s back on

 

Err if I remember right it’s

 

Admin -> client settings

 

Then I think it was something like the software evaluation policy

 

 

 

Easiest way to test this it without changing the server just log on a client, open the sccm client, go clients action and run app deployment policy

 

That will force it to run a check on the installed software

 

Steve

[hellgate24]

It should be in Client Settings in the administration tab. Maybe try manually running an "Application Deployment Evaluation Cycle" and "Machine Policy Evaluation Cycle" on one of the affected machines using the Configuration Manager control panel applet and see if that kicks it through, if it does these client timings are your issue.

[ricki]

Delete the deployment check the package and deploy it again

 

Richard

[robyholmes]

Ahh ok I'm with you. It only reports at that time not actively. Found the setting and it was set to 3 in the morning every 7 days. I'll check my test machine doing the manual method and adjust from there. Thanks!

[robyholmes]

Delete the deployment check the package and deploy it again

 

Richard

 

It's done it on a few tests now so I don't think that'll help.

[robyholmes]

So I've run the to actions mention above locally on my test machine which I know its completed the installation on. I've also ask a number of other machines via the console to do the same thing. I then waited around 5 minutes before running a summary on the deployment monitoring again. It's updated the time but the information is still exactly the same. I'll wait a little longer as I'm not sure how long these things take.

[robyholmes]

So I spotted some errors in the component status page which lead me to this fix:

https://www.enhansoft.com/how-to-increase-the-maximum-file-size-of-management-information-files-mif/

 

I've increased the limit so lets see what happens. I wonder if its not been able to get information back to SCCM to them display. We've just had a power cut onsite so while the servers are still on clients arn't going to be reporting back all that soon. So I'll leave it until tomorrow and see if machines start reporting tomorrow.

[robyholmes]

So I think I'm making some progress now. I've got the deployment status updating. It's not updating all that fast but information has changed it on so it doesn't appear to be stuck.

 

However, my deployment is still not reporting any successful installations. It has 4 which show 'Couldn't detect the software after installation' and then 10 machines showing this:

 

CI documents download timed out

 

I've found a few references to this online but mainly to do with updates which state its an update which has been superseded. I'm deploying the OneDrive client (Downloaded just before deployment last week) with the /allusers set. I detect if its already installed by checking for the exists of the onedrive.exe file in Program Files.

 

I'll try have a look at logs on the clients but it might also just need time to sort itself out. Just be nice to have at least one machine show as 'Successful' to prove I've got it setup right.

[Steve21]

It has 4 which show 'Couldn't detect the software after installation'

 

I detect if its already installed by checking for the exists of the onedrive.exe file in Program Files.

 

What rule did you use exactly for the detection? Bearing in mind 32/64bit program files etc

 

Steve

[robyholmes]

What rule did you use exactly for the detection? Bearing in mind 32/64bit program files etc

 

Steve

 

As follows:

 

I found some DTS download errors in the client log. The advice online suggested to make a change to the software so it re-saved as a new revision. I've done that and it seems to have helped a little. One or two machines have moved from the error tab to In Progress.

 

A lot of machines I'd already installed it manually so I'd expect a number of them to skip the deployment as its already installed.

[Steve21]

You have it set to type Folder not file it seems

 

*Edit - just to expand, you can do it both routes, but either onedrive.exe as file, or the folder name onedrive etc

 

Steve

[robyholmes]

You have it set to type Folder not file it seems

 

*Edit - just to expand, you can do it both routes, but either onedrive.exe as file, or the folder name onedrive etc

 

Steve

 

Your right, so would this be what I need to set:

 

Should Path end in a \ or not?

[robyholmes]

I think I've got it!

[Steve21]

Your right, so would this be what I need to set:

[ATTACH=CONFIG]58090[/ATTACH]

 

Should Path end in a \ or not?

 

Only a personal opinion, but I prefer file routes, as if for example it started updating/installing and broke it might still create folder without the files

 

But in terms of your actual question I don't think it made a difference when I did try a folder rule as long as the path is valid, normally I didn't add the last \ on though (You can do the browse method and just browse to a client and do it manually if you want to confirm though)

 

Steve

[robyholmes]

Thank you all for your help! I've just seen my first machine has been reported as compliant. I think it already have the OneDrive client on but at least its progress! I think its been a combination of a number of issues but thanks to your help I look to have solved the issues. Hopefully over the next few days more machines will show as compliant.

[Steve21]

Aye, love SCCM, lots to tweak about, but once it's sorted its amazingly powerful

 

Steve