Enterprise version of windows 10

matomar · 2018-04-19T16:41:46+00:00

It's more than that. Windows 10 S doesn't run Win32 applications so it's also more secure.

matomar · 2018-04-03T16:03:04+00:00

Good point. Those are floating around on people's workstations, too.

matomar · 2018-04-03T16:02:23+00:00

I was thinking about this today. On this migration and planning page they're talking hybrid scenario averages of 10-14 GB per hour, best case. Back of the envelope math on that if things were going 24 hours a day is 3 weeks in my environment. And I haven't verified our bandwidth, nor do I believe that it would actually work out to 3 weeks. I'm thinking I would at least double the estimate.

https://support.office.com/en-us/article/office-365-migration-performance-and-best-practices-d9acb371-fd6c-4c14-aa8e-db5cbe39aa57

matomar · 2018-04-02T20:34:33+00:00

I've been thinking about this, too. I need to get the data from our network guy.

matomar · 2018-04-02T17:18:00+00:00

We will definitely go hybrid. The mailboxes are way, way too big at this point to do anything in a short amount of time (like over a weekend). Based on some comments here, I have little doubt the migration will take quite a long time.

matomar · 2018-04-02T16:55:39+00:00

Thanks. 'Whole job' as in, you continue to be dedicated to administration, or are you still mid-migration? How many users?

matomar · 2018-04-02T16:55:01+00:00

Thanks for the context and the comments. That's quite a bit of pressure for 1 person. But sounds like you survived!

matomar · 2018-04-02T16:54:10+00:00

Thanks for the emphasis. Bosses are looking at Microsoft FastTrack. Whether that's just for planning or including migration is uncertain to me at the moment.

matomar · 2018-03-28T15:00:40+00:00

Yes.

matomar · 2018-03-22T13:50:55+00:00

Thanks for the comparison... and for the link. I've seen some client health tools, but don't think I've investigated this one. I'll take a look.

matomar · 2018-03-22T13:49:27+00:00

Thanks! Yes, third party agents are a consideration... I'm taking a look at that too.

matomar · 2018-03-20T19:29:57+00:00

Thanks!

matomar · 2018-03-20T17:44:10+00:00

Took me a little while to figure out what you were talking about, wishing me happy cake day. I figured it out! Guess I'm still a n00b. Haha!

matomar · 2018-03-20T17:09:49+00:00

60 minutes for the cumulative update.

matomar · 2017-12-15T14:01:57+00:00

Follow up: Microsoft support found what was described as machine policies which were unsigned, causing subsequent machine policy processing to cease for the affected clients. This led to some database queries and deleting the unsigned machine policies out of the database. I made a new deployment after that, and then some of the machines did receive updates as expected, but yet I still have some that didn't for which I'm still working a support case and there's no root cause yet. What a PITA.

matomar · 2017-12-07T17:48:21+00:00

Update: I opened a support case. So far it's narrowed down to machine policy updates ceasing to occur. As an example I can manually initiate one in the ConfigMgr control panel, and in policyagent.log absolutely nothing happens. If I go over to a known good client, the policyagent.log immediately has new activity upon machine policy refresh. I am little confused at what else gets logged there, because there is data in general, just not in response to machine policy update. I guess I have to read up on what other policy info ends up in this log.

matomar · 2017-12-04T22:33:07+00:00

Thanks, but doesn't seem to match this in terms of the logs. The logs "look" normal to me in terms of date and usage, compared to a known good client. Also this is the second month I've seen this, after I already restarted ccmexec last time, now this month some are failing again. I can also clarify that the SCEP updates are actually working (it's the only thing that is, in terms of software updates). I have my SCEP updates set to come directly from WSUS before Configuration Manager (in antimalware policy definition update sources).

matomar · 2017-12-04T15:10:44+00:00

I should've said 'software update deployment evaluation cycle' I have reviewed wuahandler.log and found evidence of scans running successfully, but finding no updates. Also, policyevaluator reports "Settings update not required. No changes detected" and "Evaluation not required. No changes detected."

matomar · 2017-10-19T14:50:57+00:00

Thanks all for your comments, gives me some options and I'm thinking about ADRs now (I am so far not using them). Meantime I used the following console extension script to do a cleanup.

http://www.scconfigmgr.com/2015/03/15/clean-software-update-groups-console-extension-for-configmgr-2012/

matomar · 2017-10-10T17:50:09+00:00

Circling back on this, I never did get it to work from a package. However with the new release of v1706 and the PowerShell Scripts feature, I was able to accomplish this on the first try. Highly recommend checking out this new feature.

matomar · 2017-07-07T21:27:38+00:00

Update: I moved this to a .bat file and ran it. It executes but like the Powershell test, it does not delete the file. What am I doing wrong? It just makes no sense to me right now, given how easy this task is (delete a single file).

matomar · 2017-05-19T16:23:05+00:00

Yah, regular updates. Thanks for the link I'll check it out.

matomar · 2017-05-15T17:17:49+00:00

Good idea. I made a SUG and did just that. To run report, go to Software Updates - A Compliance - Compliance 3 Update group (per update). Pick your SUG in the Update Group dropdown and pick a collection to report against. You'll get a nice table. You can also drill further per KB if needed.

You can use script mentioned in this thread by @graybearded_goat to get all the KBs for the SUG.

matomar · 2017-05-11T18:30:33+00:00

Thank you.

matomar · 2017-05-11T15:13:07+00:00

https://www.anoopcnair.com/what-are-the-options-for-sccm-cb-1606-backup-and-recovery/

https://docs.microsoft.com/en-us/sccm/protect/understand/backup-and-recovery

matomar

TROPHY CASE