How to Use Group Policy to enable Instant File Initialization
This is a post on how to use a GPO and Security Group in AD to set up Instant File Initialization on all your SQL Server instances. If you don’t know what IFI is, check out John’s post here: SQL server Instant File Initialization
This setup relies on 3 things.
1: You move all SQL Server Instances into a single OU in AD
2: You have all SQL Server Service accounts in a Group
3: You have access to AD and can Create Groups, OUs and Move Servers (Never do any of these steps in Production without talking to your Server Admin Team!!!)
Create an OU in AD (I called mine SQL Server) and moved all my servers into it.
Now create a AD Group
and add any SQL Server Engine Service Accounts.
Now the fundamentals are in place, the next step is to create the GPO, Open Group Policy Management. Navigate to your SQL Server OU, Right Click and “Create a GPO in this domain, and Link it here…”
Name the Policy (Ive named it SQL – Instant File Initialization)
Right Click on the GPO and select “Edit…”
Open up the tree to:
Computer Configuration -> Polices -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignments
Scroll down and Select “Perform volume maintenance tasks”
Double Click to open and Tick “Define these policy settings”
and Add User or Group
Hit the Browse button
Add your AD Group
Click ok and confirm you can see the group in
Close the Window. You can again confirm that the settings are in place by going to the Settings and drilling down the HTML view
Now for the GPO to take place you will need to push that GPO to the server.
To test that the GPO is in place you can do it a couple of ways
If you have Admin access to the server you can login and open the Local Security Policy from the Administrative Tools and navigate to Security Settings -> Local Polices -> User Rights Assignments and scroll down to “Perform volume maintenance Tasks”
If you dont and need to check via SQL you can go a couple of ways, heres a few: