For most corporate networks, Windows Active Directory Domain Services is the critical backbone for the support of your enterprise information structure. An improperly performing Windows Server Active Directory can be the cause of the most minor of nuisance issues, up to and including as much as the complete failure of your corporate environment’s security and authentication structure and the loss of access to your data, systems, and network shared resources.
This introduction post on the subject of the health of your Windows Server Active Directory Domain Services is part one of an occasional series of blog posts that I will have on Active Directory Health.
Performing an Active Directory Health Check in small and midsize environments can be somewhat problematic for the local, in house network and resource administrators. Often times, those smaller businesses don’t always have dedicated, full-time Active Directory administrators,…
General availability of Windows Server 2016 was announced in early October 2016.
Windows Server 2016 includes 3 main editions:
Datacenter: This is the main, large scale edition release of the Windows Server operating system, designed for corporate and enterprise environments
Standard: This edition is most ideal for small to mid-sized organizations (as well as niche uses in larger corporations) that have smaller virtualization needs and / or more of a need for a general purpose server operating system.
Essentials: This edition is mainly designed for smaller organizations, generally with less than 50 users.
Under the Standard and Datacenter editions, there are three installation options:
Server with Desktop Experience: The Server with Desktop Experience installation option (previously known as Server with a GUI) provides an ideal user experience for those who need to run an app that requires local UI or for Remote Desktop Services Host. This option has the full Windows client…
Near the end of September of this year, (2016), Microsoft formally announced that they were streamlining their technical certification program, so that it was more closely aligned to industry-recognized areas of subject matter and expertise – “Centers of Excellence, used by the Microsoft Partner Network, which identifies technical competencies that are widely recognizable by both Microsoft partners and customers.”
The Microsoft Certification program has undergone many changes in the past four or five years; many of these had been very subtle, up until now, but that wasn’t the case five years prior to that, as the program underwent a major change at that time as well.
In this blog post I will outline some of the certification program history as I experienced it over my career in the information technology field. In future posts, I will review some of the changes being…
There are a few good resources out there for setting up a clustered Master Secret Server out there:
Clustering the Master Secret Server (MSDN)
Installation of SSO on a SQL Failover Cluster
However, I faced some issues recently setting all of this up, getting the following errors (in the event log and the configuration log):
Creation of Adapter FILE Configuration Store entries failed. (BizTalk config log)
Could not import a DTC transaction. Please check that MSDTC is configured correctly for remote operation. See the event log (on computer EntSSOClusterResource) (BizTalk config log)
d:\bt\127854\private\source\setup\btscfg\btscfg.cpp(2213): FAILED hr = c0002a25 (BizTalk Config log)
Failed to initialize the needed name objects. Error Specifics: hr = 0x80004005, com\complus\dtc\dtc\msdtcprx\src\dtcinit.cpp:575, CmdLine: “C:\Program Files\Common Files\Enterprise Single Sign-On\ENTSSO.exe”, Pid: 172 (Event log)
Could not import a DTC transaction. Please check that MSDTC is configured correctly for remote operation. See documentation for details. Error Code: 0x80070057, The parameter is…
The short version of this story is: Before uploading a VHD to Azure, make sure you’ve enabled remote RDP (installing Azure PowerShell is a good idea too). But if you forget (and your VM is running Windows Server 2012), it can be fixed without having to redo a massive upload.
We recently did a demo for a prospective client, and wanted to give that client access to the VM the demo was on to further explore and tinker with the solution. Azure IaaS makes perfect sense here – upload the VM right to Azure and let the client have access. The VM can be spun up on demand, and can be removed when it’s no longer needed – and it won’t require any special permissions or network/firewall rules on either end.
There are several helpful guides to prepping and uploading a VHD…