F5F Stay Refreshed Software Operating Systems Restart the system to activate all configuration policies post-MDT installation

Restart the system to activate all configuration policies post-MDT installation

Restart the system to activate all configuration policies post-MDT installation

C
Crazy_Heaven
Posting Freak
Find
811
08-20-2016, 04:32 AM
#1
I've been using MDT for some time at work and consistently deploying Windows installations (7/10). Often, certain GPOs apply only after the computer joins my domain, while others don't. For example, Applocker and our software deployment tool are sometimes missed. To ensure full installation, a manual reboot is necessary, which can be frustrating. I've added FINISHACTION=RESTART to the default section in customsettings.ini, but it doesn't resolve the issue. Also, inserting two restart steps at the end of the TS breaks the process since it prevents logging in after a restart. I have the newest ADK and MDT versions. Have others faced this problem before? Any advice would be appreciated.
Reply
Reply
C
Crazy_Heaven
08-20-2016, 04:32 AM #1

I've been using MDT for some time at work and consistently deploying Windows installations (7/10). Often, certain GPOs apply only after the computer joins my domain, while others don't. For example, Applocker and our software deployment tool are sometimes missed. To ensure full installation, a manual reboot is necessary, which can be frustrating. I've added FINISHACTION=RESTART to the default section in customsettings.ini, but it doesn't resolve the issue. Also, inserting two restart steps at the end of the TS breaks the process since it prevents logging in after a restart. I have the newest ADK and MDT versions. Have others faced this problem before? Any advice would be appreciated.

Reply
Reply
M
Magundore
Member
Find
219
08-20-2016, 08:16 PM
#2
A planned reboot via the task scheduler may not function as intended. It seems the process depends on having the initial user log in first before applying those GPO changes.
Reply
Reply
M
Magundore
08-20-2016, 08:16 PM #2

A planned reboot via the task scheduler may not function as intended. It seems the process depends on having the initial user log in first before applying those GPO changes.

Reply
Reply
I
imTri
Posting Freak
Find
786
09-03-2016, 01:36 PM
#3
You haven't actually attempted that. You're wondering if I should add it through MDT, but the issue is I don't have to sign it. After the MDT completes, it restarts with "FINISHACTION=RESTART", yet a second restart is still needed for the GPOs to take effect. You're looking for a way to automate that second restart.
Reply
Reply
I
imTri
09-03-2016, 01:36 PM #3

You haven't actually attempted that. You're wondering if I should add it through MDT, but the issue is I don't have to sign it. After the MDT completes, it restarts with "FINISHACTION=RESTART", yet a second restart is still needed for the GPOs to take effect. You're looking for a way to automate that second restart.

Reply
Reply