Gongalong

Sorted it. It goes back to this security "fix" Microsoft put in place some months back. I had to add "Domain Computers" to the scope, as it wouldn't process the GPO without it.

Well I tried GPRESULT, and I didn't see it listed there

@Steve21 No, smaller than the image that's currently working for all users. @Rob_D I'd prefer not, because the original GPO has a ton of other stuff. The alternative I guess would be to create a third GPO that has desktop image one, then apply that to all users bar the second set of users.

Hi folks, Not a huge problem, but it’s bugging me… I’m trying to apply different wallpapers to two different sets of user accounts. We have an overall wallpaper that’s applied to all authenticated users, as part of a number of things in a GPO. I’ve created another GPO that just applies a wallpaper, and the scope for that is a handful of accounts. But it doesn’t work. I’ve tried moving the precedence ahead of the other GPO. No effect. Any ideas? Thanks

I'm doing my damndest to try and find out. As mentioned, our reseller are less than helpful. Via Microsoft's global Customer Service number I've spoken to Technical Support, Customer Service, and Partner Support. All I've learned is that the per incident cost for Windows Server is £199 + VAT. They all tell me that one of the others will provide contract costs, yet none of them can. It's ridiculous!

Hi folks, We've been using Microsoft's essentially free support with Office 365 Education, and it's pretty good. So I've been wondering, is it possible to get direct support somehow with Windows Server and the client version? We've tried to bottom this out with our reseller, but it's been like trying to get blood out of a stone. They've suggested if we bought a commercial server license it could be possible, at over £1k a year, which we'd probably we willing to pay. But is there another route? Essentially we'd want support on server and client versions of Windows. Do Microsoft offer a direct support service to customers? Thanks

Hi folks, Anyone know what the difference is between the Teacher and Administrator versions of Notebook 16.1? They're certainly very different in size, 718 vs. 2040MB. Thanks

@mullet_man Ah yes, subsequently I spotted the pinned thread on the WSUS forum https://social.technet.microsoft.com/Forums/office/en-US/5521e7f1-fa2d-4867-a47c-b276c66e6a82/windows-10-anniversary-update-1607 I didn't realise that the WSUS version was dependent on the server version, as you need 2012 (R2?) to have WSUS v4, which fully supports Win 10. But WSUS didn't seem to be our issue. We've only updated three PCs here to 1607, and they all had problems with Windows Update or WSUS. I tried a bunch of fixes, including manually downloading and installing the three 1607 CUs, and also the Win 10 Windows Update troubleshooter. In one case the latter fixed it, and the other two cases were fixed by the former. Annoying that Microsoft's QA has gone down the toilet!

Someone at another school has mentioned this, although WSUS is running on 2008R2 https://support.microsoft.com/en-us/kb/3159706

Hi folks, Anyone come across either of these issues since updating to 1607? Firstly, on the three machines I've updated to here, all three open MSN.com on login (!) on the default browser. Are MS trying to force this page upon us? Secondly, flaky Windows Update. One of the machines here is fine, but another just sticks on 0% on the Windows Update page, the other gets stuck on downloading updates at 100%. Not finding anything on either via Google. Thanks

Thanks @sted that must have been it, now works!

Ah interesting, the share only has user permissions. I've added the relevant PC group to both share permissions and security permissions. Will reboot some PCs and test! Thanks.

Odd, but perhaps I didn't have the note at its smallest size before. I'm finding that text is not display correctly, so I deleted some text which turned out to be something from somewhere else, and no undo! Showstopper.

Yes, done both of those. Will do, although I seem to have Config Manager working now so might use that instead. Publish is greyed out for me, so I've always used assigned.

I have a boundary (IP based) and boundary group in place, so not sure why automatic push isn't working, unless these need to be assigned somewhere. Also I'm still not sure why last year these PCs decided to uninstall the CM client. But I have remembered that I manually installed the client anyway, via a right-click on the device collection, as I preferred that method to ensure the client went where I wanted. This explains why I hadn't enabled automatic client distribution :-) Having manually installed the client on a couple of test PCs it's definitely installing, so I think the issue is sort of resolved, aside from why automatic push isn't working.

I've searched back in the log, which seems to cover 184 hours, and no mention of the above. I guess this raises the question, why is not trying to deploy to any of the clients that don't have the CM client?

Thanks for the reply. In ccm.log I see this essentially over and over. There are some red and yellow entries, listed below this dating from yesterday, but I'm not sure if they are significant: Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:10:29 6176 (0x1820) CCR count in queue "Incoming" is 0. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:10:30 6932 (0x1B14) CCR count in queue "Processing" is 0. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:10:30 6932 (0x1B14) Sleeping for 300 seconds... SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:10:30 6932 (0x1B14) Sleeping for 60 minutes for queue "Retry". SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:13:29 6640 (0x19F0) CCR count in queue "Retry" is 0. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:15:30 6932 (0x1B14) Sleeping for 279 seconds... SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:15:30 6932 (0x1B14) The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Default MP: SCCM.DOMAIN.local SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Certificate Store: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Checking configuration information for server: SCCM.DOMAIN.LOCAL. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) No Fallback Status Point installed on the Site SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Install on DC: False SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Option for installing using IP address: 0 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14) The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Default MP: SCCM.DOMAIN.local SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Certificate Store: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Checking configuration information for server: SCCM.DOMAIN.LOCAL. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) No Fallback Status Point installed on the Site SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Install on DC: False SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Option for installing using IP address: 0 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14) Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:28 6176 (0x1820) :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Parameters for queue: "Incoming" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Inbox Path "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Read Queue Every DIR CHANGE NOTIFICATION SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Retry CCR For 168 Hours SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Report Error After ERROR REPORTING OFF SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Warn when Queue Exceeds 100 CCRs SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Delay Between CCRs 100 Millisec SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Parameters for queue: "Retry" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Inbox Path "C:\Program Files\Microsoft Configuration Manager\inboxes\ccrretry.box" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Read Queue Every 60 Minutes SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Retry CCR For 168 Hours SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Report Error After 24 Hours SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Warn when Queue Exceeds 150 CCRs SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Delay Between CCRs 100 Millisec SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Parameters for queue: "Processing" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Inbox Path "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box\InProc" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Read Queue Every DIR CHANGE NOTIFICATION SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Retry CCR For CCR DOESN'T EXPIRE SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Report Error After ERROR REPORTING OFF SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Warn when Queue Exceeds 150 CCRs SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) Delay Between CCRs 0 Millisec SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14) :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Hi folks, I need to deploy an MSI of some client software that needs to go on all classroom PCs. I've never found Group Policy all that great at getting these sorts of things deployed. In this instance I've gone to Computer Configuration > Policies > Software Settings > Software installation, and added the MSI using New > Package, pointing to it (it's in a shared folder, which everyone has permission to access), then used "Assigned" deployment method. Despite this the MSI doesn't deploy. Any ideas what I'm doing wrong? Do I need to deploy with some options e.g. /qn? Would it be easier just to use a script with msiexec.exe /i "Filename.msi" /qn? Thanks

You can drop the font size with Ctrl+Shift+< (or > to increase font size). I tried using Ctrl+1 to drop to single line spacing, but it doesn't stick.

Bigger... in terms of screen real estate?

Hi folks, It's been a while since I've touched SCCM. I installed 2012 R2 a couple of years ago, and used it briefly to deploy some updates and one app. Around a year ago we spotted that the client had uninstalled itself from around 100 PCs (in a total of 500 or so PCs). I didn't have the time then to troubleshoot what the problem was, and it wasn't urgent to resolve. Fast forward to today, and I would like to get CM working again. One possible problem was that we changed the admin passwords across all domains, so I have deleted and added them back under Client Push Installation Properties. The WDS service was also crashing, and via some googling I found KB2910552 which has resolved that problem. But still no client deployment on the problem machines. Firewall is disabled on the machines. I've looked on some of the machines, and no C:\WINDOWS\CCM folder. Can anyone give me some ideas as to where to start looking for why the client is not installing? Thanks

Based on another thread I saw mention of a NOVA.DIR file, that's in our network SIMS folder. I copied this and put it in the local SIMS install directory and that resolved it. I'm not sure why Remote Apps don't look in the network folder.

I had a similar problem. When running Nova-T6 from SIMS on a RemoteApp server it wouldn't work as a user. It would work fine though when logged in locally to the server. Thanks to the above I looked for the NOVA.DIR file, and put that in C:\Program Files (x86)\SIMS\SIMS .net. That fixed the problem. I'd already tried putting SIMS.INI in C:\Program Files (x86)\SIMS\SIMS .net, which didn't help.

Yes, I spotted that and the Windows Ink Workspace. A shame they didn't test it a bit more!

New Sticky Notes app is still oddly buggy. Slow typing. Formatting doesn't stick. Sigh...