Server stops working for 10 minutes everyday

One of our SQL server running on Windows 2008 R2 keeps having a problem recently. Every morning around 9 AM, the users can’t access the database and we can’t login to the SQL Server. After 10 to 15 minutes, everything is normal.

1. The backup completed around 5 AM.

2. No scheduled task running at that time.

3. The only errors message in Event Viewer is related to Software Protection service:

Log Name:      System
Source:        Service Control Manager
Date:          6/8/2018 8:45:50 AM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SQLserver03
Description:
The Software Protection service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Log Name:      System
Source:        Service Control Manager
Date:          6/8/2018 8:45:49 AM
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SQLserver03
Description:
A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect.

Log Name:      System
Source:        Service Control Manager
Date:          6/8/2018 8:39:19 AM
Event ID:      7011
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SQLserver03
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SQLWriter service.

Any suggestion how to troubleshoot this issue?

Don’t see any computers in WSUS

I deployed WSUS this morning. In the ADUC, I created a new OU, HSA in our case, and move two test computers into the OU.

Image

In Group Policy Management, I enabled Windows Update as shown.

Image

In WSUS Console, make sure Use Group Policy is enabled. I also created computer group name HSA. I also run gpupdate /force. It has been  over 4 hours, I don’t see any computers in WSUS.

Image

How can we fix the problem.

Microsoft admt 3.2 password migration problem

Situation: the client followed all the steps in using admt 3.2 to migrate users and passwords but for some reason he was stuck on the Password Options Migrate passwords screen in ADMT with this message”Unable to establish a session with the password export server. The local machine does not have an encryption key for source domain ‘SERVER2012’. Please install a local encryption key. See the ADMT help for information on password migration.”

Quoted from online:

A new PES key was generated under the credentials of my TargetDomain migration account, and PES service was reinstalled on PDC.SourceDomain – – no improvement.

Contrary to the MS ADMT3.2 documentation [p65] we changed the PES service account credentials from Targetdomain\PES_account  to  SourceDomain\Mig

I can now successfully perform password migration within ADMT3.2 User Migration… using either  Targetdomain\PES_account  or  SourceDomain\Mig  as the account running ADMT on ADMT platform [GC-DC.TargetDomain.TargetForest.local]

The only outstanding question is WHY ?

– Why is the MS documentation not tallying with experience ?

– why has no one else explicitly blogged / newsgrouped this config ?

Ah well – running PES under a Source admin acocunt seems to work.

 

ADFS server issue

Our ADFS server (In LAN) and ADFS Proxy server (in Azure) have a problem. The Outlook and phone keep popup for credentials. We open a case wit Office 365 team. This is what they email to me: “we found the public IP address belongs to azure machine and requests were getting dropped while forwarding to on premise environment. As we are not trained on Azure networking part so we suggested you to open a ticket with azure team. Please update us in case of our assistance/collaboration required while working with azure team”.

Relius Web Site down

Situation: the client has a Website down issue.

Troubleshooting:
I don’t see many related events in the Event Viewer. However, I do see 6 Windows updates waiting for installing. We will schedule to install them.

To fix the problem, first of all, login the Relius web server using administrator credentials. Go to Services and restart IIS Admin Service and World Web Publishing Service.

If above doesn’t fix the problem, restart the Relius web server. It is better to restart it onsite because the site may hang and need press Enter key in console.

DHCP Relay doesn’t work Cisco SG300 switch VLAN

Situation: the client created DHCP for VoIP 192.168.20.0/24 on the Windows server.

On the Cisco SG300, he also configured DHCP Relay for VoIP VLAN. command: ip dhcp relay address 192.168.20.0, ip dhcp relay enable.

However, phone devices on VoIP VLAN don’t receive the IP addresses from the DHCP.

Troubleshooting: on «DHCP Relay Server Table» you need to add the Windows Server IP Address and then, on DHCP> Interface Settings you need to add the VLAN where you want to apply the relay.