Friday, April 20th, 2018
I had one server with an sshd service which would terminate right after starting.
The event log would have the following error:
The description for Event ID 0 from source sshd cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
sshd: PID 9960: `sshd' service stopped, exit status: 255
Not too helpful of a message.
I decided to re-run the setup with an elevated Cygwin terminal.
*** Info: Generating missing SSH host keys
*** Query: Overwrite existing /etc/ssh_config file? (yes/no) yes
*** Info: Creating default /etc/ssh_config file
*** Query: Overwrite existing /etc/sshd_config file? (yes/no) yes
*** Info: Creating default /etc/sshd_config file
*** Info: StrictModes is set to 'yes' by default.
*** Info: This is the recommended setting, but it requires that the POSIX
*** Info: permissions of the user's home directory, the user's .ssh
*** Info: directory, and the user's ssh key files are tight so that
*** Info: only the user has write permissions.
*** Info: On the other hand, StrictModes don't work well with default
*** Info: Windows permissions of a home directory mounted with the
*** Info: 'noacl' option, and they don't work at all if the home
*** Info: directory is on a FAT or FAT32 partition.
*** Query: Should StrictModes be used? (yes/no) yes
*** Info: Privilege separation is set to 'sandbox' by default since
*** Info: OpenSSH 6.1. This is unsupported by Cygwin and has to be set
*** Info: to 'yes' or 'no'.
*** Info: However, using privilege separation requires a non-privileged account
*** Info: called 'sshd'.
*** Info: For more info on privilege separation read /usr/share/doc/openssh/README.privsep.
*** Query: Should privilege separation be used? (yes/no) yes
*** Info: Note that creating a new user requires that the current account have
*** Info: Administrator privileges. Should this script attempt to create a
*** Query: new local account 'sshd'? (yes/no) no
*** ERROR: Couldn't create user 'sshd'!
*** ERROR: Privilege separation set to 'no' again!
*** ERROR: Check your /etc/sshd_config file!
*** Info: Updating /etc/sshd_config file
*** Info: Sshd service is already installed.
*** Warning: Host configuration exited with 1 errors or warnings!
*** Warning: Make sure that all problems reported are fixed,
*** Warning: then re-run ssh-host-config.
After that. The service stayed up.
Make sure you verify the access. This particular server had sshd configured for one login and of course I didn’t have the password.
Wednesday, June 29th, 2016
I had a question about the bit level of Office 2016. Sometimes I try the different versions for testing and forgot what was last installed.
Outlook happened to be open so I clicked File and selected Office Account.
This brought up the Product information but it was not listed.
I clicked the Blue Question mark About Outlook Button.
There the level was listed and it turned out to be 32-bit.
Wednesday, March 9th, 2016
Windows 10 has been an adventure. I decided to “suffer for my art” and join the Windows 10 insider testing cycle. To add to my suffering I decided to join the fast cycle which meant more releases then normal.
If you are testing many things, you can run out of disk space and like most people there isn’t time to really go through and clean. What would be nice would be a fast recovery of space.
This is possible if you want to delete the previous install of Windows 10. On average, it was about 10 gig for me.
If you are happy with the current install and will not roll back to the previous release, you can delete the previous install.
Search for Settings and open it.
- Click on System
- Click Storage
- Click “This PC (C:)“
- Scroll down and Click “Temporary Files“
Here you will see your Temporary file usage and at the bottom of the list is “Previous version of Windows”
Simple click “Delete previous versions” and start the process.
You can do other things while the cleanup runs.
As mentioned this is useful if you need space and don’t have time to do a proper cleanup. Don’t forget to look at your downloads. People forget to check that all the time. I had 27 gig *coughs*
Friday, August 7th, 2015
RSAT is one of those “must haves” for server management and scripting. It just makes work easier.
I early tested Windows 10 and there was a great deal of complaining when the preview release of RSAT stopped working. I even expressed concern over this and promptly reserved a survey about what I thought of the new look. They probably just “rolled their eyes” when I responded with I don’t care about “eye candy” when RSAT doesn’t work.
Microsoft’s response was it would be a couple weeks after RTM. Sounds hopeful but they tend to align RSAT with the server release.
Will this be the case or does a couple of weeks in Microsoft speak mean next year?
Rather annoying and it does give thought to downgrading back to Windows 8.
RSAT was released with the preview of 2016. Things are right in the Powershell universe again.
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*
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!