How to install AD DS and create forest via PS?

Here is another small tip to create a new forest on a clean Windows Server 2012 R2, it installs AD DS, DNS and necessary administrative tools, and creates your forest, DNS entries etc.

Import-Module ServerManager
Install-WindowsFeature AD-Domain-Services
Import-Module ADDSDeployment
Install-ADDSForest -DomainName lab.infralib.com -DomainNetbiosName lab -SafeModeAdministratorPassword (ConvertTo-SecureString -String "YourPasswordHere" -AsPlainText -Force) -NoDnsOnNetwork -InstallDns -DomainMode Win2008R2 -ForestMode Win2008R2 -NoRebootOnCompletion -Confirm:$false
Add-WindowsFeature RSAT-AD-Tools
Restart-Computer

Very useful information about AD DS Deployment Cmdlets can be found at http://technet.microsoft.com/en-us/library/hh974720.aspx / http://technet.microsoft.com/en-us/library/hh472162.aspx

VMWare vCenter cannot contact the specified host error while adding host.

Please search VMware web site first if you get this error and if you haven't looked to general solutions for this issue yet. You might have problems in your network configuration, DNS, IP or Lockdown mode might have enabled on the host. etc.

You may have latency issues if you still get this error and you believe your network configuration is correct.

In my case vCenter starts adding the host in retrieving mode, I can see it can communicate to my host on host's events as well.

But if fails and gives the error below.

Cannot contact the specified host. The host may not be available on the network, a network configuration problem may exist, or the management service on this host is not responding



 

I found this solution at VMware web site (Alarms about the host connection state changing from green to red frequently occur (1020210)) and added

<handshakeTimeoutMs> 120000 </handshakeTimeoutMs>

 

between <ssl> and </ssl> in /etc/vmware/hostd/config.xml file, then restarted the management agents, it resolved my issue, hope it helps.

(Restarting the Management agents on an ESXi or ESX host (1003490))



 

 

 

VMWare vCenter Server 5.5 installation on Windows 2012 R2 stuck at Directory Services Installation

I have just experienced the problem below while testing VMware vCenter 5.5 on Windows 2012 R2. It stuck at Installing Directory Services step.


I found the installer was trying to run a non-existing file "ocsetup.exe" at this step, weird thing is vCenter installer doesn't complain about that, it only waits, the log file is under %temp%\vminst.log.

1. VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Begin Logging


2. VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 --- CA exec: VMAdamInstall


3. VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Getting Property CustomActionData = 603;603;C:\Users\ADMINI~1.VML\AppData\Local\Temp\{A4400513-2688-45A9-8439-CA991F4E4106};C:\Windows\SysWOW64\;C:\Windows\system32\;C:\Windows\ADAM\


4. VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 setupApp = [C:\Windows\system32\ocsetup.exe]


5. VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 --- function: SetupComponentOnWindows


6. VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 [C:\Windows\system32\cmd.exe /c start /w C:\Windows\system32\ocsetup.exe DirectoryServices-ADAM /passive /norestart]


7. VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Util_Launch::Wait: 1 Hide: 1


8. VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Found "C:\Windows\system32\cmd.exe"


9. VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Attempting to launch ["C:\Windows\system32\cmd.exe" /c start /w C:\Windows\system32\ocsetup.exe DirectoryServices-ADAM /passive /norestart]

I copied ocsetup.exe file from a Windows Server 2008 R2 server's system32 to C:\Windows\system32 folder on Windows Server 2012 R2.

1. VMware VirtualCenter-build-1235232: 11/27/13 10:40:44 Attempting to launch ["C:\Windows\system32\cmd.exe" /c start /w C:\Windows\system32\ocsetup.exe DirectoryServices-ADAM /passive /norestart]


2. VMware VirtualCenter-build-1235232: 11/27/13 10:41:11 Process returned 0

Hope it helps.

 

 

 

Microsoft .NET Framework 4.5.1 coming to WSUS

This post was authored by Vivek Mishra on behalf of the .NET Framework team.

The Microsoft .NET Framework 4.5.1 will be made available via Windows Server Update Services on 26 Nov 2013 and this blog highlights some of the key aspects.

The .NET Framework is a development platform for building apps for Windows, Windows Phone, Windows Server, and Windows Azure. The .NET Framework 4.5.1 is a highly compatible, in-place update to the .NET Framework 4 and 4.5. The .NET Framework 4.5.1 can be installed fresh on any supported platform or can be used to upgrade your previous .NET 4 or 4.5 installation. The .NET Framework 4.5.1 also works side by side with older Framework versions lower than .NET 4.0. Applications that are based on earlier versions of the Framework will continue to run on the version targeted by default, after .NET Framework 4.5.1 is installed.

You can learn more about .NET Framework 4.5.1 here.

Useful information about this release:

1. The .NET Framework 4.5.1 and its corresponding language packs are being released for following supported platforms: Windows Vista SP2, Windows 7 SP1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, and Windows Server 2012.

2. The .NET Framework 4.5.1 Language Packs will also be available via WSUS, both to support the upgrade of previous language packs for .NET Framework 4 or 4.5 and for computers, that either have the localized version of the base operating system or have one or more Multilingual User Interface (MUI) packs installed.

3. On Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2, .NET Framework 4.5.1 is available in-box, so you do not need to deploy or install the product separately.

4. On Windows 8 and Windows RT, customers can get the .NET Framework 4.5.1 by upgrading their computer to Windows 8.1 and Windows RT 8.1 respectively. There is currently no .NET Framework 4.5.1 Windows Update offering for these 2 platforms.

5.Enterprises, that have a specific need to block offering .NET Framework 4.5.1, on computers which can directly connect to Microsoft Update servers, can do so by deploying the blocker registry key as described in following Microsoft Knowledge Base:  KB2721187:  How to temporarily block the installation of the .NET Framework 4.5.1 and its corresponding language packs

MS Güncelleme : SCCM 2012 R2 (OSD, PXE, WDS)

MS'in yayınladığı bu SCCM 2012 R2 güncellemesini özellikle OSD bileşenini ve PXE-enabled dağıtım noktalarını kullanıyorsanız kaçırmamanızı tavsiye ederim. zira WDS ve yavaş imaj transferi problemlerinizin çözümü olabilir.

Don't miss this update for SCCM 2012 R2 if you use OSD feature with PXE-enabled DPs. As it might be your saviour for your WDS or slow transfer problems.

Makaleden alıntı.

Özet

Bu güncelleme Microsoft System Center 2012 R2 Configuration Manager'de aşağıdaki sorunları giderir.

Sorun 1

Bir dağıtım noktasında (Dist. Point) a PXE rolü atadığınızda veya bir boot imajında 'Deploy this boot image from the PXE-enabled distribution point' seçeneğini seçtiğinizde WDS yani Windows Deployment Servisi duruyorsa. Ayrıca Windows Uygulama günlüğünde aşağıdaki hatasının alınması.

Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0xae4
Faulting application start time: 0x01cec5d767184634
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll

Not Bu problem sadece site sucnularındaki dağıtım noktalarını etkiler.

Sorun 2

İşletim sistemi imajının SCCM 2012 R2 istemcisine indirilme işlemi daha eski versiyona sahip SCCM 2012 istemcilerinden uzun sürüyor olması.

Kurulum

Bu güncelleme Central Admin. ve Primary sitelara, yönetim konsollarına ve istemcilere uygulanır. Site sunucusuna kurduğunuzda size istemci güncelleme paketi oluşturma imkanı da sunar.

Site sunucularına kurulumdan sonra boot imajlarının update edilmesi gerektiğini unutmayın.

Tam makaleye http://support.microsoft.com/kb/2905002 adresinden ulaşabilirsiniz.

 

MS Update for SCCM 2012 R2 (OSD, PXE, WDS)

Don't miss this update for SCCM 2012 R2 if you use OSD feature with PXE-enabled DPs. As it might be your saviour for your WDS or slow transfer problems.

Excerpt from the article.

Summary

This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.

Issue 1

After you enable the PXE Service Point role on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running. Additionally, entries that resemble the following are logged in the Windows Application log:

Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0xae4
Faulting application start time: 0x01cec5d767184634
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll

Note This problem affects only distribution points that are installed on site servers.

Issue 2

When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behaviour when the target client is running Windows PE or a full Windows operating system.

Installation information

This update applies to Central Administration sites, primary sites, administrator consoles, and clients. Applying this update to a site server will let you create client update packages.

After the update is installed on site servers, any operating system boot images should be updated.

Notes

• All existing media (such as stand-alone, boot, or prestaged) that use existing boot images (default or custom) will have to be re-created.


• To fully fix the problem in Issue 2, the client side .msp file has to be installed during the "Setup Windows and ConfigMgr task by using the PATCH= command.

Full article can be reached at http://support.microsoft.com/kb/2905002