I find myself quite often trying to keep straight all the different replication activities that can occur within an Active Directory (AD) domain.
There is:
Intrasite Replication
Urgent Replication
Intersite Replication
Intersite Change Notification Replication
Reciprocal Replication
Immediate Replication
Manual Replication
With the advent of Windows Server 2012 R2, Microsoft has worked diligently to provide support for virtualization and allow corporations to reduce costs by virtualizing as much hardware as possible. New features in 2012 R2 help prevent USN rollback and/or Lingering objects via the new VM-Generation ID. If a guest o/s is restored from a snapshot the VM-Generation Id that is stored in the DIT (msDS-GenerationID attribute on the DC’s computer object) is compared to the value on the Host. If they don’t match then the Invocation-Id is updated with a new value and any RID’s from the machine are replaced with a new set from the RID Master.
So the question is, “Do I need a physical DC in my Domain?” Continue reading “Can I Virtualize ALL My DC’s In the Domain?”
Ace here again. I thought to touch base on DNS zones, and more so, focus on what AD integrated zones are and how they work. This blog almost mimics my class lecture on this topic. Check back for updates periodically, which I will notate with a timestamp above with whatever I’ve added or modified.
This topic was also briefly discussed in the following Microsoft Technet forum thread:
Technet thread: “Secondary Zones?”
http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/c1b0f3ac-c8af-4f4e-a5bc-23d034c85400
Group Policy can be difficult to design, implement, and troubleshoot unless you are fully aware of the foundational concepts that drive Group Policy with Active Directory. There are many moving parts with Group Policy, not to mention the reliance that Group Policy has on Active Directory functioning properly. When making changes within a Group Policy Object (GPO) in hopes for a desired outcome, only to have Group Policy not working correctly can be very frustrating.
many article is founded in internet about its problems. one of the best articles about reason for failing apply GPO is writen by derek melber. please check these links
http://www.windowsnetworking.com/articles-tutorials/windows-server-2008/Top-10-Reasons-Why-Group-Policy-Fails-to-Apply-Part1.html
http://www.windowsnetworking.com/articles-tutorials/windows-server-2008/Top-10-Reasons-Why-Group-Policy-Fails-to-Apply-Part2.html
http://www.windowsnetworking.com/articles-tutorials/windows-server-2008/Top-10-Reasons-Why-Group-Policy-Fails-to-Apply-Part3.html
thanks by www.windowsnetworking.com
last week , i try to work with Windows 2008 R2 server but my system restart frequently . after research i find Reboot problem. If these servers are using File Share or SMB v.2, srv2.sys may cause this problem.
Srv2.sys driver is root cause of this problem.
This is SMB 2.0 server driver. You can download hotfix KB2552033 for Windows Server 2008 R2 SP1 with your own risk until Microsoft officially release it.
I am sure you must have experienced VPN reconnect – a new IKEv2 based VPN tunnel that is added in Windows 7 that allows automatic and seamless switchover of an active VPN connection when the underlying Internet interface (connection) changes thus maintaining application persistence.
Isn’t that COOL – like VPN user moving from Wifi to WWAN and back – giving a true mobile connectivity to corpnet ! Yes it is…
This means, Windows7 in-built VPN client and Windows 2008 R2 in-built VPN server (aka RRAS) supports following VPN tunnels:
About each folder under the SYSVOL share in Domain Controller
SYSVOL folder used to store a copy of the domain’s public files like system policies, Group Policy settings and logon/logoff scripts, which are replicated to all other domain controllers in the Active Directory domain through File Replication Services (FRS), You can find many folders inside the SYSVOL share, I would like to explore and explain each folder by how it’s used in the process of SYSVOL replication.
trusting domain and the trusted domain
For the diagram above, we have the following summary:
When you create a trust from the Account Domain (trusted), the type of trust will be “incoming trust”.
When you create a trust from the Resource Domain (Trusting), the type of trust will be “outgoing trust”.
Remember that Direction of Trust is the opposite to Direction of Access.
Here is the list of all articles about Direct Access Technologies. i need to configure Direct access for students , so they must reading articles.
this article is useful for helping
http://www.227volts.com/?p=1216
http://techontip.wordpress.com/direct-access-series/
http://www.labo-microsoft.org/articles/Direct_Access/1/
When you are facing slow logons into domain and you also get events 1030 and 1006 you need to look into your network. By default Kerberos uses UDP packets to communicate. You need to force Kerberos to use TCP instead of UDP by changing registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\ Kerberos\Parameters
If it doesn’t exists just create it 
Create DWORD key called MaxPacketSize and set it to value 1.
For more infor there is official KB http://support.microsoft.com/kb/244474/en-us