Windows PowerShell 3.0 is now available to download for Windows 7, Windows Server 2008 R2, and for Windows Server 2008. Windows PowerShell 3.0 comes in the Management Framework 3.0. You can download Windows PowerShell 3.0 from the Microsoft Download Center. You need to download the appropriate package for your target operating system. Windows 7 and Windows Server 2008 R2 must have at Service Pack 1, and Windows Server 2008 requires Service Pack 2. There are a number of enhancements in Windows PowerShell 3.0 including workflow, new cmdlets, and improvement language features.
Audit account logon events
Event ID Description
4776 – The domain controller attempted to validate the credentials for an account
4777 – The domain controller failed to validate the credentials for an account
4768 – A Kerberos authentication ticket (TGT) was requested
4769 – A Kerberos service ticket was requested
4770 – A Kerberos service ticket was renewed
Audit account management
Event ID Description
4741 – A computer account was created.
4742 – A computer account was changed.
4743 – A computer account was deleted.
4739 – Domain Policy was changed.
4782 – The password hash an account was accessed.
4727 – A security-enabled global group was created.
4728 – A member was added to a security-enabled global group.
4729 – A member was removed from a security-enabled global group.
4730 – A security-enabled global group was deleted.
4731 – A security-enabled local group was created.
4732 – A member was added to a security-enabled local group.
4733 – A member was removed from a security-enabled local group.
4734 – A security-enabled local group was deleted.
4735 – A security-enabled local group was changed.
4737 – A security-enabled global group was changed.
4754 – A security-enabled universal group was created.
4755 – A security-enabled universal group was changed.
4756 – A member was added to a security-enabled universal group.
4757 – A member was removed from a security-enabled universal group.
4758 – A security-enabled universal group was deleted.
4720 – A user account was created.
4722 – A user account was enabled.
4723 – An attempt was made to change an account’s password.
4724 – An attempt was made to reset an account’s password.
4725 – A user account was disabled.
4726 – A user account was deleted.
4738 – A user account was changed.
4740 – A user account was locked out.
4765 – SID History was added to an account.
4766 – An attempt to add SID History to an account failed.
4767 – A user account was unlocked.
4780 – The ACL was set on accounts which are members of administrators groups.
4781 – The name of an account was changed: Continue reading →
Windows 2008 ile birlikt kullaniyorduk replication tool’ u daha sonra 2008 ve 2008 R2 ile gelmedi ama bir sekilde bunlarin uzerinede kuruyorduk. Simdi artik yeni versiyonu var ve oldukcada guzel ve cogu uzmanin bekledigi bir tool… Asagidaki linkten daha detayli bilgi almak mumkun iyi calismalar…
Bir kaç örnek 🙂
- Introducing Windows Server 2012
- Introducing Windows Server 2008 R2
- Introducing SQL Server 2012
- Introducing SQL Server 2008 R2
- Understanding Virtualization Solutions
If you are trying to run ADPrep /RODCPrep and have the error similar to:
Adprep could not contact a replica for partition DC=ForestDnsZones,DC=Domain,DC=com
Adprep encountered an LDAP error. Error code: 0×0. Server extended error code: 0×0, Server error message: (null).
You may have invalid entries for the fsmoRole owner of DomainDNSZones and ForestDNSZones. Have you decomissioned a domain controller recently or upgraded from 2003 to a 2008 domain? If so, check the following:
- Open ADSIEdit
- Click Connect and type in the value DC=DomainDnsZones,DC=domain,DC=com
- Expand it and check the properties for the “Infrastructure” object
- Under the attribute “fsmoRoleOwner” you may see a corrupt value for an OLD domain controller which is no longer in existence. If you see a value such as 0ADEL:4da956af-53f1-4962-a100-5ee4c8477c88 then this is the problem
- The value should be CN=NTDS Settings,CN=DCSERVERNAME,CN=Servers,CN=SITENAME,CN=Sites,CN=Configuration,DC=domain,DC=com
- To obtain the correct string for stage 5, under ADSIEdit expand CN=Sites, CN=<site where Infrastructure Master server is located>, CN=<server name> and go to properties of CN=NTDS Settings
- Copy the distibguishedName attribute
- Replace the value in stage 5 with the correct value
- Perform the above AGAIN for the value DC=ForestDnsZones,DC=domain,DC=com
To export AD group members to text:
dsquery group DC=consoto,DC=com -name groupname | dsget group -members > groupname.txt
*Note: command to be run on DC.
This tutorial will describe how to deploy a MSI on multiple machines by using Group Policy.
- 1. Methods of deployment
- 2. Create a distribution point
- 3. Create a Group Policy Object
- 4. Assign a MSI package
- 5. Publish a MSI package
- 6. Redeploy a MSI package
- 7. Remove a MSI package
- 8. Troubleshooting Active Directory/GPO deployments
Group Policy supports two methods of deploying a MSI package:
Storage Manager for SANs helps you create and manage logical unit numbers (LUNs) on Fibre Channel and iSCSI disk drive subsystems that support Virtual Disk Service (VDS) in your storage area network (SAN).
A LUN is a logical reference to a portion of a storage subsystem. A LUN can comprise a disk, a section of a disk, a whole disk array, or a section of a disk array in the subsystem. Using LUNs simplifies the management of storage resources in your SAN because they serve as logical identifiers through which you can assign access and control privileges.
- To install and start working with Storage Manager for SANs, see Deploying Storage Manager for SANs.
- For an overview of managing LUNs with Storage Manager for SANs, see Overview of Storage Manager for SANs.
- For a list of steps about how to create a LUN using Storage Manager for SANs, see Checklist: Prepare and Create a LUN.
- For information about the connections between the servers in your SAN and the LUNs that you create using Storage Manager for SANs, see Manage Server Connections.
- To create and manage LUNs, see Manage LUNs.
- To create and manage targets on iSCSI subsystems, see Manage iSCSI Targets.
- For information about Fibre Channel and iSCSI subsystems, see Manage Subsystems.
- For information about disk drives in the Fibre Channel and iSCSI subsystems, see Manage Drives.
- For information about DiskRAID, see DiskRAID.