Hello World, I'm back with Powershell scripting and Migration table. If you remember, in some previous posts, we have demonstrated how to generate a migration table using powershell. In this post, we have seen how easily it was to create a migration table by querying Active Directory domain to retrieve the gpo list. In this second post,
Hello world, In this post, I will provide a little extra information about the Powershell script used to generate Migration table. If you remember, we have discussed in this previous post how to generate migration table using powershell script. In this specific case, we had access to the source domain. The script was retrieving the list of
Hello World, A few months ago, we explained how to migrate GPOs between domains. If you remember, when you are performing a migration between domains and you want to migrate Group policies between them, you generally needs to generate a "migration table". This migration table can be used to translate specific domain information such as
Hello world, This post will describe a common problem within distributed IT infrastructure: transfer of files over slow networks. The post will provides an efficient way to transfer the files over networks by using Powershell cmdlet and a technology called BITS (Background Intelligent Transfer service). Ready ? So let’s go ! Problem
Hello World, Lately, I'm working a lot with Powershell scripting. My customer needs to automate a bunch of tasks related to Active Directory. The infrastructure is based on Microsoft Technology and we can use SCCM infrastructure to efficiently deploy and schedule the tasks to be run by the script. You would think that deploying Powershell
Hello World, Today, I have some free time and I want to post a Powershell script related to the SPN (Service PrinicpalName). The Problem As you probably know that in an Active Directory infrastructure, SPNs should be unique but time to time, you might have duplicates SPN in your environment. Because I'm working on automating a bunch of
Hello World, In a previous post, we have seen how you could backup the dns zones to text files using a mix of powershell and dnscmd.exe. Now, it's maybe time to check how you can use this backup files in order to restore your dns infrastructure in case of a problem (you have deleted a dns zone). The principle of this script is similar to the
Hello World, Based on some comments and feedback received on the post about backing up DNS Zones, we have decided to publish a new version of the script. The logic remains the same. The main difference with the previous one is that we are using better the powershell capabilities. Special thanks to Jeffrey Hicks . This version
# ---Note: A newer version of the script is available here Hello World, Today, I want to post a short powershell script. I've been asked if it was possible to create a powershell script to perform backup of DNS zones. First thing that came into my mind was to use the dnscmd.exe command line that can be used to automate a
Hello World, This is the batch file sample that can be used to automate the setup of a TFTP/PXE server on a windows 2003 box. Some limitations apply on this "basic" batch file. The limitations are the following : batch file has been tested on windows 2003. batch file as is will not work on Windows 2008. DHCP service should be installed
