Windows Updates restart now or later option appears to all users on the Terminal Server

Just as the title suggests, Windows Update pops up notifications to restart the server now or later to all users on a Terminal Server.  I ran into this yesterday when I had installed a security update and a few miscellaneous ones as well.  I figured that the restart notifications would only be shown on the administrator accounts and not all users on the Terminal Server.  That proved to be a bad assumption on my part, but a logical one.  Why would regular users need to be notified that the server needed to be rebooted to finish installing updates when they don’t even have the security permissions to do so?

Anyway the Chief Financial Officer e-mailed me wondering what was going on later in the afternoon.  She and other users were getting really annoyed by the constant pop up to restart the server ( shoot I would be too!).  So in the end I told her to restart the server and that was the end of the problem.  Why couldn’t Microsoft restrict these updates notifications and restart pop up’s to only the administrator accounts?  Maybe there is a registry setting that I just don’t know about that could do all this for me, but for now I’ll just remember to schedule these updates during off hours.

  • Share/Bookmark

NTBackup error (1f)

I just ran into a problem where a daily exchange backup was not completing successfully. The error NTBACKUP gave me was (1f) which is because it could not find the backup file (.bkf) that it created for the backup set.

I went to the shared drive where the backup file should have been saved, and sure enough it was gone. I watched it for a day just to see if it would create the file by itself, but that proved to be false. It looks like NTBACKUP needs to already have the backup file in the right location for it to run the backup job successfully.

To solve the problem, I recreated the backup file that it was looking for in the shared folder. I did this by doing the following:

filenew

1. Right click
2. Choose “New”
3. Select “Text Document”
4. Type the exact name of the file that ntbackup needs.
5. Make sure you change the file extension to .bkf or it ntbackup will not use it.
6. Done.

After that the backup jobs started to run successfully again without a problem. I am still not sure why the original file disappeared but that’s not really important at this point.

  • Share/Bookmark