Adding a physical secondary domain controller backup to our virtual engineering environment

Here’s a fun one. I have a secondary domain controller that I have taken a backup of and converted to a virtual machine.

I’ve added this to our cloud engineering environment (an exact mirror of the physical system with the exception of it was previously missing the SDC) but when I try to boot I get the c00002e2 error.

I can boot up in Active Services Repair mode (safemode bluescreens) but before I can log in it starts shutting down again for no apparent reason.

Related:

Local DNS lookup always fails first time

On a very small number of Windows 10 machines at my work we have an issue where lookup of local domain names always fail to be resolved, but only for the first request.

The following is the output from a command prompt, a number of lookups were made one after the other, with no other commands in between.

C:\Users\Me>nslookup mail2
Server:  UnKnown
Address:  192.168.50.199

*** UnKnown can't find mail2: Server failed

C:\Users\Me>nslookup mail2
Server:  UnKnown
Address:  192.168.50.199

Name:    mail2.mydomain.local
Address:  192.168.3.27


C:\Users\Me>nslookup backup
Server:  UnKnown
Address:  192.168.50.199

*** UnKnown can't find backup: Server failed

C:\Users\Me>nslookup backup
Server:  UnKnown
Address:  192.168.50.199

Name:    backup.mydomain.local
Address:  192.168.3.23


C:\Users\Me>nslookup elrond
Server:  UnKnown
Address:  192.168.50.199

*** UnKnown can't find elrond: Server failed

C:\Users\Me>nslookup elrond
Server:  UnKnown
Address:  192.168.50.199

Name:    elrond.mydomain.local
Address:  10.0.0.59

The following is an IP config just so you can see the network setup.

C:\Users\Me>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : XPS13-2
   Primary Dns Suffix  . . . . . . . : mydomain.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : mydomain.local

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . : mydomain.local
   Description . . . . . . . . . . . : Dell Wireless 1820A 802.11ac
   Physical Address. . . . . . . . . : 74-DF-BF-30-12-B1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::34ea:a41a:612c:d401%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.50.219(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 19 January 2017 08:28:58
   Lease Expires . . . . . . . . . . : 27 January 2017 08:28:59
   Default Gateway . . . . . . . . . : 192.168.50.1
   DHCP Server . . . . . . . . . . . : 192.168.50.199
   DHCPv6 IAID . . . . . . . . . . . : 91545535
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-34-C3-F9-74-DF-BF-30-12-B1
   DNS Servers . . . . . . . . . . . : 192.168.50.199
                                       80.64.54.19
   Primary WINS Server . . . . . . . : 192.168.50.199
   NetBIOS over Tcpip. . . . . . . . : Enabled

DNS Server is a Windows Server 2008 (Standard) machine, which is also the DC/AD server.

Related:

.Net Framework 3.5 not being installed on Windows Server 2008

Server : Windows Server 2008 (Standard) Service pack 2

All website running before on Framework 3.5 was stopped working and was giving error :

Error Code : 0x80070032
Config Error : The configuration section ‘appSettings’ cannot be read because it is missing a section declaration

So I tried to repair & re-install framework 3.5 but it was giving error while repairing or re-installing. Even it was not allow to uninstall it.
So uninstalled it by using Clean-up utility given on this link – http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx
Now there is no framework 3.5 on server but it is not allowing to install it. Just gives message “Setup Error“, no more detail and leaves success message in Event Viewer

Product: Microsoft .NET Framework 3.5 SP1 — Installation completed successfully.

Other message in event viewer is

Windows Installer installed the product. Product Name: Microsoft .NET Framework 3.5 SP1. Product Version: 3.5.30729. Product Language: 0. Installation success or error status: 0.

Is there any solution to install it?

Edit:
there are couple of update installed showing in Windows update and there are two update available. but Windows is not able to install. and Windows not allowing to uninstall those installed update and gives message the action is only valid for products that are currently installed
In C:\Windows\assembly folder it still show .net 3.5 related entries (System.Core, System.Data.Linq etc.)

Edit:
log file dd_clwireg.txt content (it generates only this log file) :

[01/18/17,07:45:49] !Begin Microsoft .NET Framework Registration Correction Tool
[01/18/17,07:45:49] The following product GUIDs were specified on the commandline:
[01/18/17,07:45:49] {2FC099BD-AC9B-33EB-809C-D332E1B27C40}
[01/18/17,07:45:49] {B6EC01E7-431D-4D29-B9D4-E1D74CAF0AB0}
[01/18/17,07:45:49] {72EB0C4F-A51D-4203-B841-E529F6C4F571}
[01/18/17,07:45:49] {7131646D-CD3C-40F4-97B9-CD9E4E6262EF}
[01/18/17,07:45:49] {B508B3F1-A24A-32C0-B310-85786919EF28}
[01/18/17,07:45:49] {340DFCEA-8855-4722-99B3-1BBAC5DDC088}
[01/18/17,07:45:49] {0ADCF9F9-7EA9-48B5-9656-D65B2B246203}
[01/18/17,07:45:49] {89BF6CBE-A47A-4CAB-AE77-D0D5A234CCA5}
[01/18/17,07:45:49] {F7855754-13F5-426B-B090-5875FAFF1B20}
[01/18/17,07:45:49] {2BA00471-0328-3743-93BD-FA813353A783}
[01/18/17,07:45:49] {F1A37352-02A5-4F9A-A902-B9537DE1086F}
[01/18/17,07:45:49] {2C8F9A07-43F7-4C31-9401-21B0CFAD94D3}
[01/18/17,07:45:49] {9C93EC33-91B7-4900-8D88-15E5695440C9}
[01/18/17,07:45:49] {15095BF3-A3D7-4DDF-B193-3A496881E003}
[01/18/17,07:45:49] {491DD792-AD81-429C-9EB4-86DD3D22E333}
[01/18/17,07:45:49] {7D1B85BD-AA07-48B8-808D-67A4067FC6BD}
[01/18/17,07:45:49] {BAF78226-3200-4DB4-BE33-4D922A799840}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {2FC099BD-AC9B-33EB-809C-D332E1B27C40}
[01/18/17,07:45:49] INFO: no patches were found under product {2FC099BD-AC9B-33EB-809C-D332E1B27C40}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {2FC099BD-AC9B-33EB-809C-D332E1B27C40}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {B6EC01E7-431D-4D29-B9D4-E1D74CAF0AB0}
[01/18/17,07:45:49] INFO: no patches were found under product {B6EC01E7-431D-4D29-B9D4-E1D74CAF0AB0}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {B6EC01E7-431D-4D29-B9D4-E1D74CAF0AB0}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {72EB0C4F-A51D-4203-B841-E529F6C4F571}
[01/18/17,07:45:49] INFO: no patches were found under product {72EB0C4F-A51D-4203-B841-E529F6C4F571}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {72EB0C4F-A51D-4203-B841-E529F6C4F571}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {7131646D-CD3C-40F4-97B9-CD9E4E6262EF}
[01/18/17,07:45:49] INFO: no patches were found under product {7131646D-CD3C-40F4-97B9-CD9E4E6262EF}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {7131646D-CD3C-40F4-97B9-CD9E4E6262EF}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {B508B3F1-A24A-32C0-B310-85786919EF28}
[01/18/17,07:45:49] INFO: no patches were found under product {B508B3F1-A24A-32C0-B310-85786919EF28}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {B508B3F1-A24A-32C0-B310-85786919EF28}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {340DFCEA-8855-4722-99B3-1BBAC5DDC088}
[01/18/17,07:45:49] INFO: no patches were found under product {340DFCEA-8855-4722-99B3-1BBAC5DDC088}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {340DFCEA-8855-4722-99B3-1BBAC5DDC088}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {0ADCF9F9-7EA9-48B5-9656-D65B2B246203}
[01/18/17,07:45:49] INFO: no patches were found under product {0ADCF9F9-7EA9-48B5-9656-D65B2B246203}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {0ADCF9F9-7EA9-48B5-9656-D65B2B246203}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {89BF6CBE-A47A-4CAB-AE77-D0D5A234CCA5}
[01/18/17,07:45:49] INFO: no patches were found under product {89BF6CBE-A47A-4CAB-AE77-D0D5A234CCA5}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {89BF6CBE-A47A-4CAB-AE77-D0D5A234CCA5}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {F7855754-13F5-426B-B090-5875FAFF1B20}
[01/18/17,07:45:49] INFO: no patches were found under product {F7855754-13F5-426B-B090-5875FAFF1B20}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {F7855754-13F5-426B-B090-5875FAFF1B20}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {2BA00471-0328-3743-93BD-FA813353A783}
[01/18/17,07:45:49] INFO: no patches were found under product {2BA00471-0328-3743-93BD-FA813353A783}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {2BA00471-0328-3743-93BD-FA813353A783}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {F1A37352-02A5-4F9A-A902-B9537DE1086F}
[01/18/17,07:45:49] INFO: no patches were found under product {F1A37352-02A5-4F9A-A902-B9537DE1086F}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {F1A37352-02A5-4F9A-A902-B9537DE1086F}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {2C8F9A07-43F7-4C31-9401-21B0CFAD94D3}
[01/18/17,07:45:49] INFO: no patches were found under product {2C8F9A07-43F7-4C31-9401-21B0CFAD94D3}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {2C8F9A07-43F7-4C31-9401-21B0CFAD94D3}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {9C93EC33-91B7-4900-8D88-15E5695440C9}
[01/18/17,07:45:49] INFO: no patches were found under product {9C93EC33-91B7-4900-8D88-15E5695440C9}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {9C93EC33-91B7-4900-8D88-15E5695440C9}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {15095BF3-A3D7-4DDF-B193-3A496881E003}
[01/18/17,07:45:49] INFO: no patches were found under product {15095BF3-A3D7-4DDF-B193-3A496881E003}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {15095BF3-A3D7-4DDF-B193-3A496881E003}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {491DD792-AD81-429C-9EB4-86DD3D22E333}
[01/18/17,07:45:49] INFO: no patches were found under product {491DD792-AD81-429C-9EB4-86DD3D22E333}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {491DD792-AD81-429C-9EB4-86DD3D22E333}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {7D1B85BD-AA07-48B8-808D-67A4067FC6BD}
[01/18/17,07:45:49] INFO: no patches were found under product {7D1B85BD-AA07-48B8-808D-67A4067FC6BD}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {7D1B85BD-AA07-48B8-808D-67A4067FC6BD}
[01/18/17,07:45:49] !!Begin removing or fixing missing patch registration for all patches under product {BAF78226-3200-4DB4-BE33-4D922A799840}
[01/18/17,07:45:49] INFO: no patches were found under product {BAF78226-3200-4DB4-BE33-4D922A799840}
[01/18/17,07:45:49] !!End removing or fixing missing patch registration for all patches under product {BAF78226-3200-4DB4-BE33-4D922A799840}
[01/18/17,07:45:49] DEBUG: Final error code 0 - returning zero.
[01/18/17,07:45:49] !End Microsoft .NET Framework Registration Correction Tool

Related:

Windows 2008R2 smtp traffic cannot leave the box

I have a weird situation where an Orion NPM server on a Windows 2008R2 box cannot connect to the mail server in our environment. The application logs show that it is indeed trying to connect but fails; however, a wireshark packet capture does not show any SMTP traffic leaving the system, no RSTs or anything, just blank. It is able to see all other traffic so it is sniffing traffic properly but i’m at a loss as to what could be blocking it. Windows firewall is completely off and disabled. The antivirus does not have a firewall extension/component to it. Even trying to telnet to port 25 on the destination fails. We’re thinking that it’s not an application issue because a different Orion server with the same app configuration is able to connect and we are able to see the traffic in wireshark.

If someone could point me in the right direction I would greatly appreciate it. Thanks!

Related:

Internet Explorer IE11 launches in Enhanced Security for Users despite setting in Server Manager

Our users log on to an RDP server running Windows 2008 R2. I have already gone into Server Manager and disabled ESC for both admins and users. While the setting is applied for admins, users still go into ESC when they launch IE11. I’ve already checked the registry settings and they reflect the appropriate settings from the Server Manager.

What else can cause users to launch into ESC?

Can a user tell IE to start without ESC?

Related:

Lync 2010 Endpoint was unable to register

So after deploying a Standard edition of Lync 2010, When testing the outside connectivity I’m getting an error: The endpoint was unable to register.

I make sure everythins was properly in place: DNS entries on external DNS and open ports on the outside firewall.

Here’s the output:

Test Steps
Testing remote connectivity for user lync2010@lync.mydomain.com to the Microsoft Lync server.
Specified remote connectivity test(s) to Microsoft Lync server failed. See details below for specific failure reasons.
 Tell me more about this issue and how to resolve it

Additional Details
Couldn't sign in. Error: Error Message: The endpoint was unable to register. See the ErrorCode for specific reason.

Error Type: RegisterException.
Deregister Reason: None.
Response Code: 504.
Response Text: Server time-out.

I have ran a portscan on a box I have on the public Internet and all ports are actually open:

[ec2-user@ip-xx-xxx-xxx-xx ~]$ nmap xx.28.99.xx

Starting Nmap 5.51 ( http://nmap.org ) at 2013-07-01 13:30 EDT
Nmap scan report for www.mydomain.com (xx.28.99.xx)
Host is up (0.020s latency).
Not shown: 997 filtered ports
PORT STATE SERVICE

443/tcp open https

444/tcp open snpp

5061/tcp open sip-tls

The public IP on this server is NATted through a Firewall, so my external config will look something like this:

SIP Access:
lync.mydomain.com
Port: 5061
Protocol: TLS

SIP Access:
lync.mydomain.com
Port: 444
Protocol: TLS

SIP Access:
lync.mydomain.com
Port: 443
Protocol: TCP

Both servers are reacheable within each other, Front-End and Edge. I can’t seem to find any solution to this.

Related:

Windows Server Backup "Reading Data; please wait…"

On windows Server 2008 R2 I have recently added the windows server backup (WSB) feature.

Opening WSB I get the message “Reading Data; please wait…”. This message fails to go away, even after leaving the server for over 12 hours. I also notice in the task manager that svchost.exe (username: networkservice) is using all available processing power. So I terminated that process and then WSB comes on-line.

However after restarting the server and WSB the issue reoccurs. WSB also fails to recognize my store-in-go flash drive (2gb).

What is the underlying problem here?

Related: