We made it to Friday, October 7th! Not only is it Friday, but it is also World Smile Day.
Snap! FortiGate firewalls, Pixel 7, Neeva, Cat's Eye Nebula, Uranus, & more Spiceworks Originals. :)Or, you know, if you don't have a pet dinosaur, you can post other, lesser dinosaurs, since I suppose it is their month too. October is International Dinosaur Month, so let's see those SpiceRex pics, taken in the wild. Discovered that there was a database update that needed to be applied overni. Our IT Manager is out for vacation, which is not a big deal, but there are often days when staff are needy. Yesterday was a day.In-Office was insane. Overnight Database updates, found myself looking at the business end of a taser! Water Cooler. Invoke-Command -Session $session -ScriptBlock īy adding in a semicolon we can of course add a second line to our ScriptBlock and make the process a little more automated. The challenge i had was that on several clients it seemed Symantec had a different IdentifyingNumber (IN), which is the GUID used by Windows to identify the product.Īs there were only 7 client machines i did a lot more of this manually than perhaps i needed to.įirstly i found the right IdentifyingNumbe r from each PC. I already had the machines on the network configured for PowerShell Remoting, so connecting to them was not a challenge. There are various ways of course to execute a command on a remote machine, you can use PSTools’, PSExec for example, but i prefer to use PowerShell where i can. 
I did a lot of searching around for a reliable solution, most of which came back to using MSIEXEC from a command line. It was a small SEPM deployment, only 7 clients and a server but i was surprised to be reminded that SEPM has no ‘uninstall’ tool from their console. Finally moving my last client from Symantec SEPM to Trend Micros WFBS Hosted platform.
0 kommentar(er)
