Just a really short post on an issue I saw a little while back which I’ve been meaning to get round to documenting.
Whilst working on VM optimization project, I booted up one of my VMs for testing and received the above message during the OOBE stage. The reason for this is because I disabled one of the scheduled tasks which I thought looked fairly innocuous, CloudExperienceHost. Turns out this is important to leave enabled, even if you don’t want your VMs connecting to the cloud as the Out of Box Experience uses it. Specifically, the task can be found under:
Arguably there are newer and more fancy ways to do this in recent iterations of SCCM. If you wish to set up a standard internet facing SCCM environment or just an SSL secured environment this is the old skool way.
CREATE SCCM CERTIFICATES
Open CA | Right-Click Cert Templates > Manage
Right-Click Web Server template > Duplicate template
Open new duplicate template : a Request Handling tab: Check ‘Allow private key to be exported’ b General tab : Change name to “ConfigMgr IIS Cert”, validity 5 years c Subject name : default (‘supply in the request’ should be checked) d Security tab : remove the ‘Enroll’ permission from Domain Admins and Enterprise Admins, add your SCCM_Site_Servers group and add Enroll and read permission to this group | Click OK
Open new duplicate template : a Compatibility tab: keep defaults (ensure Windows Server 2003) b General tab : Change name to “ConfigMgr DP Cert”, validity 5 years c Security tab : Add your SCCM_Site_Servers group and add Enroll and read permission to this group | Click OK. Remove ‘Enroll’ for Enterprise Admins. On Request Handling tab, select Allow private key to be exported
Open new duplicate template : a Compatibility tab: keep defaults (ensure Windows Server 2003) b General tab : Change name to “ConfigMgr Client Cert”, validity 5 years c Security tab : Click ‘Domain Computers’ group and add AutoEnroll and read permission to this group (don’t uncheck ‘enroll’) | Click OK
Open CA | Right-Click Cert Templates > New > Certificate Template to issue
Select the three new certs from the ‘Enable Certificate Templates’ box. | Click OK
Open the GPMC, open default domain policy (or wherever you have your PKI policy) a Windows Settings > Security Settings > Public Key Policies > Trusted Root Certification Authorities b Open up ‘Certificate Services Client – Auto-Enrollment’. Change ‘Configuration Model’ to ‘Enabled’ c Check ‘Renew expired certs…’ and ‘Update certificates that use cert templates’
ADD CERTS TO SCCM
On the DP open the certificate MMC > Computer > Personal > Certificates | Right-click folder > All Tasks > Request New Certificate
Next > Next | On ‘Request Certificates’ page check ‘ConfigMgr DP Cert’ and click ENROLL > Finish
While still in the certs MMC, Right-click the DP cert you have just imported > All Tasks > Export > Next. Select Yes, export private key
Keep defaults on Personal Information Exchange – PKCS #12 (.PFX) and click next.
Enter a password > Next > Save the file as C:\Temp\SCCM_DP_Cert. Click finish
On the MP open the certificate MMC > Computer > Personal > Certificates | Right-click folder > All Tasks > Request New Certificate
Next > Next | On ‘Request Certificates’ page check ‘ConfigMgr IIS Cert’ and click ‘moe information is needed…’ link
Under Subject Name, select ‘Common Name’ and add the name of the server, eg SCCMMP01 > Add
9.Under Alternative Name, select DNS and add the FQDN of the server > Add
Under the GENERAL tab, add the name of the server as the friendly name
Under the Cert Authority tab, select your CA if it’s not already selected. Select Enroll > Finish.
On the MP (internet facing if there is one) open IIS > Default Web Site > Bindings… | Edit HTTPS
Select the new SSL certificate. If you don’t see HTTPS, click add and create it.
Repeat the above on any other MPs
From the SCCM console go to Admin\Overview\Site Configuration\Sites | Properties > Client Computer Communication. Add the Root CA Certificate you created earlier.
FINALLY!!!! Go to Admin\Overview\Distribution Points | Properties and add the certificate and password you created on the DP in point #5. Rinse and repeat for all your DPs.
Just select YES if you get a message about it being a copy of one used on another DP.
To add certs for the SUP/WSUS see https://www.petervanderwoude.nl/post/how-to-configure-a-software-update-point-to-use-ssl-for-communicating-with-wsus/
I have just had to
do this so I thought I’d make the most of the ordeal by documenting. I make no
apologies here – I am giving you the bare minimum click-by-click. I’m not
attempting to tell you what you’re doing along the way as this post will just
be too long. As long as you do everything as indicated and don’t take any
shortcuts, you should be fine. If you previously had a CA in place, I recommend
you fully uninstall them before starting.
You will need two
VMs, one domain joined (IssuingCA) and the other just in a workgroup (RootCA).
In my example below, my rootCA is SVR-CA-01.bondynet.org and my Issuing CA is
SVR-CA-02.bondynet.org. These names make up some of the cert names in the instructions
below so please ensure you substitute as appropriate for your environment. One
final caveat : this was put together on Windows 2012 R2 so there maybe one or
two minor changes to the interface in places but honestly not much has changed
Workgroup computer, Install cert services
Go thru config wizard, Select: a Cert Authority b Standalone CA c Root CA d New private key e All default crypto options f Default names g Default Validity (5 years) h Default db locations i Click CONFIGURE
Open Cert Authority > Properties > Extensions > CRL Distribution Point (CDP) a Click Add.. and under location type : http://svr-ca-02.bondynet.org/CertData/<CaName><CRLNameSuffix><DeltaCRLAllowed>.crl (replace with your issuing CA) b Check Include in CRLs… c Check Include in CDP extension… d Select AIA from cbobox > Add AIA e http://svr-ca-02.bondynet.org/CertData/<ServerDNSName>_<CaName><CertificateName>.crt (note the crt extension and the underscores for AIA). f Check ‘Include in the AIA extension…’ g Restart services when prompted.
Publish CRL by going to Revoked certificates node | right click > all tasks > Publish
crl and crt published at C:\Windows\system32\CertSrv\CertEnroll. Copy this path to clipboard.
ROOTCA properties > General > View Certificate #0 > Details > Copy to file > Next DER Encoded > Next > save as C:\Windows\system32\CertSrv\CertEnroll\RootCACert.cer
Browse to \IssuingCA\C$\Temp\Certs and drop the three certs in the folder
PUBLISH ROOT CA IN AD
Open the GPMC, open default
domain policy (or some other if preferred)
a Windows Settings > Security Settings > Public Key Policies
> Trusted Root Certification Authorities
b Right-click > Import > Next > browse to \IssuingCA\C$\Temp\Certs\RootCACert.cer
> Next > Finish
Run GPUpdate /force and you
should see your new certificate appear under ‘Trusted Root Cert
Authorities’ in Certificate manager MMC.
Install Certificate Authority with all Role Services
Once complete, in SVRMGR click the yellow triangle for post config.
Specify creds or leave default | Next
Select Cert Auth, Cert Auth Web Enrollment | Next
Select Enterprise | Next
Subordinate CA | Next
Create a new private key | Next
All default crypto options | Next
All default names | Next
Default req filename and location (C:\SVR-CA-02.BONDYNET.org_BONDYNET-SVR-CA-02-CA-2.req) | Next
Default db location | Next | Configure | OK. Don’t configure additional roles when prompted for our purposes here.
REQUEST CERT FROM PARENT CA
On the root CA, browse to \\IssuingCA\C$ and copy c:\SVR-CA-02.BONDYNET.org_BONDYNET-SVR-CA-02-CA-2.req locally.
In CA MMC console > | Right click > All Tasks > Submit New Request > Select SVR-CA-02.BONDYNET.org_BONDYNET-SVR-CA-02-CA-2.req > OK
Go to Pending Node to see the new certificate. Right-click > All Tasks > Issue
Under ‘Issued Certificates’ node, right-click > Open > Details tab > Copy to file > Next
Select Cryptographic Message Syntax Std (.P7b) and select ‘Include all certs in path’. | Next
Open Browse and you should be in the CertEnroll directory. Call the cert ‘IssuingCACert’ | Next | Finish | OK | OK
Copy the new .p7b certificate to the \IssuingCA\C$\Temp\Certs\ location.
INSTALL & CONFIGURE CERT ON ISSUING CA
Create a new folder at C:\inetpub\wwwroot\CertData
Copy the .crt file and the .crl file from C:\Temp\Certs to C:\inetpub\wwwroot\CertData
Open the CA console on the Issuing CA. Right-click servername > All Tasks > Install CA Certificate. Select The new p7b certificate.
The business of adding a front end for a PXE-driven SCCM OS build is generally a pretty important consideration if you want to specify some basic information prior to deployment. It’s also something that I’ve felt has never been properly addressed by the SCCM development team. To be fair you could argue it’s not their job to do this but with more functionality being adding to every single aspect of SCCM in every new release, it does feel like something that probably should be looked at in the future.
For now, there are plenty of examples of great front ends on the internet – look up ‘Pretty Good FrontEnd’ by Johan Arwidmark or ‘Pretty Good Front End Clone’ by Maik Koster. These two have been around donkey’s years. One of my favourites is Nicolaj Andersen’s very neat ConfigMgr Front End which offers a whole world of features. Additional infrastructure is necessary to accommodate this however, in the form of web services.
So why create another? Well I’m certainly not pretending to set the world alight with some kind of ingenious new approach but I always felt there was just a little too much fiddling about with most of the solutions I saw elsewhere. What I wanted was something I could ideally just drop straight into my WinPE image which would just work. There are certainly features I could add (and may indeed do so if enough people ask) such as ability to remove certain sections, eg, domain, OS, etc. However in an effort to keep things simple I have left this for now.
The Front End
This is a typical illustration of what it looks like in my lab. Most aspects are configurable via a small ini file (yes I know it’s a bit 90’s but let’s face it, it’s a damn sight easier to use than an xml file for this kind of thing). The ini file below is configurable for the OUs in your environment, the domain (or domains) and even colour and font size. One area I went a little off the beaten track is the ability to select different images you want to use in your task sequence. This is great in my lab as I often want to test stuff out on different OS’s and will routinely add a new image when necessary to my tried and trusted task sequence. As such I’ll detail this a little more.
If you want to use the same task sequence but have different images available in that sequence, you can enter them in the ini file. Just be sure to enter the appropriate option/filter in appropriate task sequence step. For example, in the image above we have a number of different OS’s which relate to separate images. Under the INSTALL section of your task sequence you might have one or more separate steps to Install Windows 10, Install Server 2016, etc. On each of these steps, click Options and add a Task Sequence Variable condition, eg:
TS VARIABLE: OSDImageEquals <Windows 10 1803>
It is important that the text in the OS box above equals the OSDImage value of your condition.
Of course, you can just add a description in the Config.ini file instead and have one image step in your task sequence with no condition set and all will be well. I suspect this is what most people will want. The option to do it this way is just there if you want it.
Typical Config.ini settings below. This file must always exist in the exact same folder as the NewFrontEnd.exe executable.
:: [ORG_UNIT] - Enter all OUs you want displayed in format OU=Dept, OU=Org, DC=domain, DC=suffix one after the other.
:: [DOMAIN] - In most cases, this is more for show but can be used to build a workgroup machine too if WORKGROUP is specified underneath the primary domain.
:: [OS] - If your task sequence can build more than one image, add it here, eg Windows 10 1607 LTSB. Then add a task sequence variable condition called OSDIMAGE and equal it to the image name in your TS.
:: LOGO, recommended max size is approx W:120, H:120 for a font size of 8-10
:: BACKGROUND, Enter standard OS colour names, eg Red, DarkRed, Marroon, MidnightBlue, etc
:: FONTSIZE, recommend, 8-10 but it will go bigger. Seems to jump in 2s, eg, 8,10,12, etc. This has a bearing on the size of the form.
:: FONTCOLOR (American spelling, sorry) see BACKGROUND, above.
:: SMSTSPREFERREDADVERTID, If specified, enter the Deployment ID of the task sequence you want to run. This will override any other advertised task sequence either 'available' or 'required' and the wizard won't show.
:: HIRESDISPLAY, If HIRESDISPLAY=True the size of the form is increased so it doesn't get 'scrunched up' on the display. This has been tested against a Surface Pro 4.
:: NOTE - [ORG_UNIT], [DOMAIN] and [OS] should all have at least one value (ideally) so the interface has something to show. Settings under [MISC] can be removed or ignored by adding a semicolon before the setting.
Windows 10 1803
Windows 10 1607
Windows Server 2016
Windows 2012 R2
Windows 10 1607 LTSB
Windows Server 2008
So how do you get this working in WinPE?
Create a share somewhere and drop NewFrontEnd.exe, Config.ini and your company logo png into it (and/or possibly RunFEUI.vbs – see end of post)
In SCCM go to your chosen boot image, right-click | properties | Optional Components. Select Microsoft .NET (WinPE-NetFx). This is a C# application so it needs this option available in your boot image binaries.
Select the Customisation tab. Under Prestart Command Settings enter “X:\sms\PKG\SMS10000\NewFrontEnd.exe”
Select Include files for the prestart command
Select the share you created above with the files in for the source directory.
If you want to, add a background, click OK and you’re done. After the update distribution points wizard has completed, double check the Last Update information in the bottom section of the SCCM console to ensure the time matches the time you ran the wizard and everything has updated as it should. This is important as it hasn’t usually finished updating just because the wizard progress bar has completed.
For The Adventurous.
One of the neat things about using the above method is that there is no ugly command prompt in the background as it brings up the front end interface. However the downside of this is that all the files are inside your WinPE image so if you want to update them you have to go through the above process once again which is both time consuming and laborious. One solution though is to simply point to a script that will map a drive to a share that exists elsewhere on your network and execute the files from there instead. This facilitates updating the files on the fly.
In the zip file included below, there is a file called RunFEUI.vbs. Simply open it and edit it to fit your environment (ie edit line 4 with the appropriate drive mapping and account).
Had a tag-team of problems with Office 365 Client updates and this one reared its ugly head just a I managed to successfully get the O365 updates syncing successfully.
Under Software Library|Office 365 Client Management|Office 365 Updates none of the client updates were checking in as ‘required’. Given that the O365 client on 5000-odd machines was at version 16.0.8201.2207 (v1705) this seemed odd to say the least. Everything was set correctly in SCCM for O365 Client Deployment so the summary screen should theoretically be showing that the whole estate needed at least every version beyond this.
After some considerable digging I discovered that for updates to work in SCCM, the CDNBaseUrl and the UpdateChannel settings in the registry MUST BE IDENTICAL. In my case, whoever had packaged the application had a bogus entry in the UpdateChannel setting that made no sense. I copied the CDNBaseURL setting (something along the lines of http://officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60) into the UpdateChannel setting, restarted the Microsoft Office Click-To-Run service and ran an update scan and update deployment policy refresh from the SCCM control panel applet. Immediately O365 client updates showed up as required. This can be checked under the following ConfigMgr report:
Compliance 8 – Computers in a specific compliance state for an update (secondary)
I then set up a GPO to push this URL out to the estate and watched the count increase.
I have recently been doing some work for a customer who has introduced OneDrive to their estate. For reasons known only to them, they have insisted that their users have their OneDrive storage restricted to only 1GB. Not much in today’s money.
The issue that I have been seeing (on more than one occasion) is that OneDrive would run out of space (denoted by a red cross over the blue cloud icon) yet if you were to look at what the folder contained, clearly there should be space left. On one occasion there should have been as much as 700MB left so I was left scratching my head as to why it was complaining it was full.
This is what has worked for me when I have come across the above scenario, and mainly involves removing the versioning feature, which by default will store 500 major versions.
Completely clear out the local OneDrive folder. Cut and paste the data into a local temp folder somewhere, eg C:\Temp\OneDrive
Right-click OneDrive icon and select View Online.
Select Recycle Bin from the menu on the left. Click Empty Recycle Bin. This can take a little while sometimes, be patient and ensure it’s properly emptied.
Once empty you should see a line at the bottom of the screen: Can’t find what you’re looking for? Check the Second-stage recycle bin. Click the Second stage recycle bin link.
Delete everything in the second-stage recycle bin.
Click the cog/gear icon in the top right of OneDrive. A setting menu should open. Select Site Settings.
Under Site Settings | Site Administration click Site libraries and lists.
Click Customise “Documents”
Click Versioning Settings.
Under Create a version each time you edit a file in this document library? select No versioning.
Select OK at the bottom of the screen.
Recommended: Remove OneDrive from the computer. Also ask user to save any profile related settings (favourites, desktop icons, etc) and remove user’s profile in System|Advanced Settings|User Profiles|Settings
Get the user to log back on and restore the user’s desktop and favourites.
Reinstall OneDrive. Once configured, copy user data back to the user’s local OneDrive directory and wait to sync.
The above steps were successful in releasing the ‘used’ space. Bare in mind, no version history will be kept in this scenario so please ensure that this is acceptable first. Without step 12, I did see the problem come back in one instance so if possible, I’d strongly recommend this step. You must bare in mind that when this procedure is carried out, it is like the user logging on for the first time and any customisations to their local profile WILL BE LOST.
All http://officecdn.microsoft.com is whitelisted and available, definitely no issue there.
All other updates seem to come down fine.
There are no ADR rules at all in place.
Running a full sync produces the error below:
My client downloads updates through a proxy server and naturally the correct details for the proxy were in place on the Site System Settings under Site System Roles. Also the checkbox for Use a proxy server when synchronizing software updates was checked under the Proxy And Account Settings tab under the Software Update Point Properties role.
Despite the fact that ADRs were NOT created or used in any way, it transpired that the checkbox Use a proxy server when downloading content by using automatic deployment rules also had to be checked. Once this was selected, O365 updates started syncing.
Difficult to pick a snappy title for this so suggestions welcome!
Anyway, I had an issue recently where we needed to load test 100+ machines, all booted from PXE. All machines were fresh out the box and all ethernet adaptors were fully registered in SCCM in the ignore list. In short, there was no reason for any machine not to PXE boot as expected. All went well until the 29th machine and then every machine thereafter refused to PXE boot. However, they did still receive an IP address. Additionally, the message Server response timeout E-18 flashed up very quickly before booting from the SSD.
Digging a little further, the machines that were able to PXE boot fine had to receive an IP address between .2 and .31 to work. Any IP after just refused to work. Having accepted that all was well from a firewall perspective, I was forced to concede that the problem was somehow local.
To cut a long and boring story short, the problem turned out to be a mis-configured subnet mask on the PXE server, in this case 255.255.255.224 instead of the 255.255.255.0 that it was supposed to be. The PXE server itself was allocated an IP within the range of PXE bootable clients and anything outside the range didn’t work. So easy when you know but one expects the basics to be correct so it took a while to track down. Hopefully this will provide some more ideas for anyone else who finds themselves with a similar issues.
I recently had a request by a customer to disable WiFi on their laptops. I know, crazy, right? They had their reasons though and it was a temporary solution to a problem. The issue with disabling Wifi is that there isn’t actually a group policy which directly allows ‘disable wifi’ but the workaround is pretty easy. Essentially we need to disable the WlanSvc service.
What we need is to harness group policy preferences, so without further ado here goes:
Create a new GPO. Browse to Preferences | Control Panel Settings | Services. Right click in the right-hand pane and select New | Service. Call it WlanSvc.
In the properties, change Startup to Disabled
Ensure the service name is WlanSvc. Note, you’ll probably not be able to find this service if you browse via the ellipses unless the machine you’re using for administering group policy is a laptop. This is why it’s important you name the service correctly.
Under Service Action change to Stop Service.
5. Apply the group policy. Note, you will probably need to reboot the machine for everything to take effect properly. You may notice a short pause before full (wired) network connectivity kicks in, maybe about 20 seconds. After this you should see that wireless is disabled.
I recently had an issue where a site seemed to suddenly stop communicating with it’s management point and the SUP. Whilst I never got to the bottom why it actually happened (given that all was working fine a day or two before) I did eventually get to the bottom of how to fix it but it took a good day out of a very busy schedule.
Anyway, the symptoms were an MP and SUP which could no longer communicate with the SQL DB. The logs would have errors similar to ‘Call to HttpSendRequestSync failed for port 80 with status code 500’.
As you can see, what a mess. This was working fine previously!
The MP in question was on the same domain and used the computer account to communicate with the database which was on the primary site server. I had also configured an account to connect to another forest on the SCCM site but this wasn’t used in conjunction with this MP. After banging my head against a wall for an hour or two I nonetheless decided to remove the forest connection account from ConfigMgr but still the same error. I then came across this post which I applied. This caused the mpcontrol.log and the WSUSCtrl.log to both calm down somewhat:
OK both logs looked better but we’re still stuck with errors. I decided to take a look back at the SPNs for SQL. I opened ADSIEDIT, found the SQL account in question and looked at the Service Principal Names registered. Sure enough they seemed to be registered with the NETBIOS and FQDNs all as expected.
Balls. I was running out of ideas.
I had a chat to my SQL guy and he suggested running Kerberos Configuration Manager just in case. This utility will check if the SPNs are registered correctly, and if not register them all correctly for you. Basically, it takes the messing about out of the command line. I wish I’d known about this utility years ago. Sure enough, it said one of the registrations was incorrect for some reason and it ‘corrected’ it. These worked fine the day before so why had one stopped working?? Doesn’t matter, just need to fix…
After that everything started working again. I was happy. Hopefully this will help someone else frustrated with bugs they didn’t know of in SCCM and SPNs that look, for all intents and purposes, like they are otherwise registered.
Headaches of an SCCM Admin. But no other symptoms yet.