You’ve written this wonderfully detailed and formatted document, updated your Table of Contents and your Tables of Figures and Tables… and realised you missed the fact that all your Table were being captioned as Figures.
There are two ways I know to correct it, both are manual though and you just need to pick the one that works best for you.
Here’s a neat tip to speed up the WDS / PxE boot times for your OSD deployments. This should work on pretty much any WDS (and RIS?) servers you have.
http://www.sccm.biz/2013/05/how-to-boost-up-pxe-tftp-boot-speed.html#!/2013/05/how-to-boost-up-pxe-tftp-boot-speed.html
Create this in registry on Your PXE WDS Server:
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\DP\RamDiskTFTPBlockSize
Type Reg_Dword
Value: 16384 Dec (Do not use higher value than this!)
((Recommend that you increase this setting in multiples (4096, 8192, 16384, and so on) and that you not set a value higher than 16384.))Restart WDS Service
Remember the higher value the more risk of packet loss if bad network Connection.
You have to try this out carefully in your network environment.
If experiencing problems, try lower value.
Here’s a quick script I’ve written to generate a log of my servers windows backup results. It connects to each server and log the start time of the backup operation and the “Successful” time. If there is no “success” due to an error then it just won’t return anything.
Have you only got a server or two and not much budget to work with? I’m guessing you might also be using the built in Windows Backup?
There isn’t actually much wrong with using Windows Backup. It does the job, just without all those extra features of paid-for backup solutions. One big missing feature for example is notifications of backup results.
So here’s a quick and easy way to keep track of those backups. It’s not the neatest solution, but it is better than nothing!
A quick reference to this link for troubleshooting 500.19 errors on IIS
http://blogs.iis.net/webtopics/archive/2010/03/08/troubleshooting-http-500-19-errors-in-iis-7.aspx
After an unexpected server shutdown, I was cleaning up various issues. One thing was to remove an old WSUS install that was no longer used. It turns out this didn’t cleanup all the settings and left a “bad” DynamicCompression library enabled.
So for me, scenario 6 sorted the problem out.
This is considered a pedantic point by many people I work with, but it’s something I still work to change.
When Microsoft released System Centre Configuration Manager, the natural abbreviation/acronym that myself and pretty much everyone else used for it was “SCCM”. Makes sense.
At some time I recall that Microsoft started to make a point of telling people *not* to call it SCCM. I can’t seem to find any official Microsoft reference to this though. (If you know where an official Microsoft statement is, please let me know)
The reason is that Microsoft do not have any rights to “SCCM”, and also to prevent any possible confusion with another organisation that is already known as SCCM.
At this point I’ll hand over to the following links to explain:
Unfortunately, SCCM is deeply ingrained into the vocabulary of the people that work with it, so it’s going to take a while (if ever) to change. I’m doing my part where I can. I will still tend to tag things with “SCCM” to help other people who are using it as a search term, but when referencing it in any documents I will use “ConfigMgr” or “CM[version]” (e.g. CM07, CM12) instead.
If you happen to notice me slipping in an “SCCM”, feel free to berate me over it.
Annoying stuff I figured out (or am trying to) 