Saturday, June 20th, 2015
I had a messed up automounter and wanted to restart it. Sometimes I just draw a blank for the command. It could be that I am focused mainly on Windows these days and I simply forget the command. Who knows?
It’s simple really,
service autofs restart
If I needed to start it:
service autofs start
To get a simple status:
service autofs status
Now that I have written this; it should remain.
Posted in Linux
Wednesday, June 17th, 2015
I am “crash and burn” testing windows 10. Painful but a good way to get the feel of it. One painful loss was the Active Directory module for Powershell. You have to have Remote Server Administration Tools (RSAT) and they stopped working for Win 10. There was a special release for the January version of Win10 but it died with the May version and Microsoft reported they will fix it with the general release.
What to do?
I thought about using one of my test VMs running Windows 2008. It had RSAT but when I tried to import the Active Directory module into Powershell; I received an error saying it did not exist.
I found there were a extra other steps needed to be done:
1) Import-Module ServerManager
2) Add-WindowsFeature RSAT-AD-Powershell
After that, I was able to import the active directory module.
There was a recent update to windows 10 and it nuked RSAT. Microsoft will basically fix it after the OS is released. *sighs*
Posted in 2008, PowerShell, Windows
Tagged 2008, Active Directory, powershell, Windows 10
Friday, June 5th, 2015
I am early testing windows 10. Overall I am liking the OS but it has it quirks and issues. My biggest issue involved the Juniper Pulse client no longer functioning.
I recently upgraded to release 100130 and found the pulse client not working and the OS required activation.
The product key had changed and the new one would not take. The error basically said the wrong product key is in play?
I tried many things and nothing worked. Then, I remembered I was testing the Enterprise version.
A quick check of the site and sure enough there was a different product key. I used it and the OS activated.
The pulse client decided to be a pain again. It would take the token and then sit forever with a message about securing the tunnel.
I installed the latest build of but the problem remained. I removed and installed the client and this time it was able to connect!
Posted in 10, Windows
Tagged juniper pulse, Windows 10