IIS Set Connection String in web.config using the Web-Administration powershell module
So in the web.config file for “MyApplication” application under “Default Web Site”, I have a connection string called “MyChartsConnection”, that I want to change the connection string as I am modifying it for Production use , changing server name and username password, plus some parameters that i do not need in test. Continue reading…
Occurs on any .net framework 4.6.1 and higher. It is due to the CLR.DLL.
Upgrading the .Net framework will not fix it.
CLR.DLL version 4.7.2102.0 to 4.7.2558.0 is the issue
What will fix it is Continue reading…
The following script contacts all the windows servers in the domain and returns a list of stopped services that are set to Automatic to a CSV file. Continue reading…
In the setup event log you see KB3139398 and probably a bunch more KBs failing to install Continue reading…
HP Workstations
https://support.hp.com/us-en/document/c05869091
HP Servers
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00039267en_us
More here
MS operating systems
VMWare advisory
https://www.vmware.com/security/advisories/VMSA-2018-0002.html
List of issues relating to November 2017 Patch Tuesday Windows Updates
I found the reason I could not see any user_sid or user_displayname data when running Get-DesktopVM.
So this script get a list of users logged into computers. It uses my personal favourite RDS PowerShell module but works on PCs. Note: some firewall rule(s) inbound may be required. Continue reading…
SCCM is a bit fiddly it has its “own” powershell console that is a tad inconvenient. Also a lot of assumptions are made that the user is all good to go with SCCM cmdlets and that is usually far from the truth.
The following script is does few prerequisite checks to ensure it is all good to go for the novice SCCM Powershell user. The script is self documenting as to what checks I am doing. These check have been learnt the hard way. 🙂
For the novice:
All SCCM Cmdlets have to run from the $SCCMSiteCodePath Location
Assumption is that the Security group ($SecurityGroupthatHasSSCMRights in the code) does have the correct rights to run the powershell functions against SCCM
So these are the reasons I see for the Status Message error 1025