Decided to setup a openvpn server on a new CentOS 7 box and it was not exactly straight forward so below are the steps required, this should be enough to get started
The following allows you to package up your build output into a SFX file with custom properties that appear when someone right clicks the SFX and chooses properties.
Useful if you need to create a zip that can be signed but want your company/product information to appear on the SFX.EXE.
Just a quickie. I have a script that outputs an XML file and I use an XSL file to display it but Management wanted HTML files, the thought of having to re-code the output was disheartening to say the least. I then came across “msxsl.exe” it’s a Microsoft tool that takes a XML file and a XSL file and then generates the resultant rendered output in HTML.
I was doing some testing on TFS and got fed up queuing new builds via right-click -> queue new build -> ok. So here is a powershell script that can be used to kick off a build.
I’ve included some extra assemblies that don’t need to be used as I have other functions that do use them in the same module file. example useage below
Sorry for the lack of progress until recently but I’ve recently had a lot of more important priorities in life so working on this had to go on hold for a little while. I am hoping in the next few months to release version 1.0 but as on now this is still experimental so should only be used in a lab environment.
Please use the ticketing system on sourceforge to report any issues and add feature requests.
Well I’ve just been put in charge of managing our TFS infrastructure so here is the first of hopefully many posts around automating and managing TFS.
The attached script runs a SOAP query against the TFS Warehouse Cube and returns the jobs and their status and then either generates an HTML file or sends an HTML email with the results.
I recommend creating a directory called Scripts on the C:\ drive and setting the permissions so that only the System Administrator & User the script runs as can access the contents of the directory.
This is a script I wrote over a year ago but have only just rediscovered, I can’t remember if it works / or if I ever used it in production. But hopefully will be of use to someone (assuming it works).
If anyone tries it please respond and let me know how worked / any issues you had.
This is a script that parses the smsbkup.log and outputs results (in html) and the relevant portions of the file to the specified folder. The idea being that the with a small bit of tweaking you could have the report hosted on a webserver to check or emailed (there will be a post on emailing in Powershell later) to you.
This is best run from the central primary under credentials that have access to the other sites.
Note: The script requires UNC paths for the $fpath variable as it is expecting be be run remotely.
Note2: This script was written for SCCM 2007 and not for SCCM 2012, however thanks to one of my readers, Satish, the following should fix that:
Change if ($content | where {$_ -like "Backup task completed successfully*"}) {
to if ($content | where{$_ -like "*SQL Backup task completed successfully*"}) {
Note3:
Potential Dates issues with SCCM 2012 R2. Thanks to Marius for the update.
Change $cdate = $cdate.adddays($days) | get-date -format “ddd MMM dd”
to (this is probably US specific and will probably vary depending on locale) $cdate = $cdate.adddays($days) | get-date -format “MM-dd-yyyy”
Recently I had an issue where ActiveSetup wasn’t installing some applications when deployed. It turned out that it was due to some of the packaged applications not having a program with the Windows installer information populated. As it was believed that this may not an isolated issues I was tasked with producing a report of all Packages where the information was missing. This is not actually possible via the default reports as none of the views exposed to SCCM actually contain this information. The only way to get this information is to query the SCCM database table “PkgPrograms”, and to do that and have a permenant report SSRS is needed as it can run with the credentials of the user generating it or with an execution account which may have more access.