Monthly archives: October 2008

Timothy

RD Tabs with Server Core

You can use RD Tabs even with Windows Server 2008 Server Core installations.  All you have to do is enable Remote Desktop on the server from the command line.  Great tip!

Timothy

Scheduling a Reboot in Windows Server

It's really amazing to me how many people don't realize how easy it is to schedule a reboot on a Windows server.  Sure, you can just wait for Windows Updates to kick in once a month in the middle of the night, but sometimes you need a reboot tonight because you installed/changed something.

Here's how you do it (the easy way)...

Log onto your Windows server as an administrator.

Open up Scheduled Tasks.  Create a new task.  Set the application to "C:\windows\system32\shutdown.exe -r -t 0" (-r means reboot, -t means wait this many seconds -- zero in this case, so it will reboot immediately).  If you have a misbehaving service that doesn't shut down in a timely fashion, you can add -f (force shutdown) but I'd recommend against this on a server unless you absolutely need it.  Forcing a shutdown causes Windows to kill any task not responding to a graceful application exit.  You may not want to open that can of worms on a production system!

Start the app in any folder, but I always use c:\windows\system32 since that's where the binary is.

Set the "Run As" user to NT AUTHORITY\SYSTEM.  Doing this allows you to not have to worry about password expiration or account lockout since it's running directly under the system context.  When the task asks for a password, leave it blank.  Keep in mind only admins can delegate the scheduled task impersonation account to the system itself.  (If anybody else could do it, Windows would have a massive security hole!)

After setting the account, you will notice the "Run As" field will be blank.  This is a UI bug in the task scheduler.  If you click OK and then re-open the task, it will show up as NT AUTHORITY\SYSTEM.

Task Scheduler Screenshot

Now, set the time to reboot in the "Schedule" tab. 

You are done!

Easy!

Timothy

Mystery of the Failing Exchange 2003 Auto Accept Agent

At work, I maintain an old Exchange 2003 box which is the company's biggest work horse.  It's old, dusty and outdated, but it works hard and occupies a special place in my silicon heart.

Anyway, I was tasked with adding a new Auto accept agent so that a new conference call number could be booked through Outlook calendar appointments as a resource.  This is all pretty basic Exchange 2003 stuff here.

The problem was I kept getting a strange error when running RegisterMailbox.vbs...

Error 80070426: The service has not been started.

I double checked and the Auto accept agent's service was running.  What gives?

It turns out that the error message is misleading.  What actually happened is my user account did not have the appropriate permission to a DCOM service.  Checking the Event Viewer is what clued me in.  In there I saw...

 Event Viewer DCOM Error

The devil is in the details, listed below...

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{9DA0E103-86CE-11D1-8699-00C04FB98036}
to the user domain\user.  This security permission can be modified using the Component Services administrative tool.

I fired up Component Services, expanded DCOM, found the CLSID for the module, and looked at the Activation permissions.  I was surprised to see that Administrators was not in the list, which  must be why this error is occurring.

image

I added Administrators and granted the group Local Launch and Local Activation.  After that, Auto accept agent worked once again!  Mystery solved.

Timothy

My State is Full of Awesome

I never thought I'd see the day when a liberal presidential candidate would have a stable two-week lead in the polls in my wonderful home state of North Carolina, with the potential for it to carry to election day. Maybe Asheville and the RTP area are beginning to overshadow the more traditionally conservative areas?

Yes, I'm quite liberal (Obama is actually a bit too "right wing" for me, but I still think he will do a fine job). I'm a bleeding heart artist, so my political viewpoint should come as no great surprise.

  • Rasmussen Poll for NC - October 2, 2008

This state is still very much a toss-up, so I'm not celebrating yet. However, my wife has stated that she will, in fact, dance in the streets should Obama carry NC. I, for one, would love to see that. Maybe I'll take pictures when she's not looking.

Blog

Search Posts

Recent Comments

  1. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Tom: Thank you Edward! After beating my head against a wall for days, tried your suggestion out and lo and...

  2. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Mike: DPM 2016 setup will fail if you have SQL Server Management Studio (SSMS) V17.x installed. Re-Install...

  3. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Rob: Edward, thanks man! you were a lifesaver. My scenario was Win Server 2016 from scratch, SQL 2016 (N...

  4. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Edward: It also crashes with the 4387 error if you have the SQL Management Studio 17 tools installed. Installing...

  5. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Ram: Hi - I followed richsmif instruction and was able to successfully install DPM 2016 on SQL 2016. Completed...

  6. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Neighborgeek: Thanks for the post, this is exactly the issue I am running into. I'm disappointed to see that you didn...

  7. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    richsmif: I have DPM 16 working with SQL 16. Install SQL 16 first, don't touch, install DPM 16 , upgrade...

  8. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    ptbNPA: That should have been *ID 810*, not 820

  9. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    ptbNPA: For anyone else coming across this in the future and have an ID 820 error: For some strange reason...

  10. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Timothy: Sorry, I don't have any other insight. I'm sure you ran into all the same articles I did about the error...

Archive

Tag Cloud