daneil16 Posted December 11, 2015 Posted December 11, 2015 Hi guys, Just a quick query really, going to google afterwards anyway but like to hear your thoughts. I want to upgrade our MDT2012 to the new 2013 Update 1 for our Windows 10 roll out. I am just wondering whether I can just install the 2013 Update 1 install straight on 2012, or do you have to install MDT2012 update 1, MDT2013 and then then install 2013 Update 1. Also is there anything people came across that might be helpful Thanks as always. Dan
sted Posted December 11, 2015 Posted December 11, 2015 a couple of issues ive found on a fresh install (im still testing it not willing to roll it out yet) it creates the deploymentshare$ share with dumb permissions such that even mdt itself cant make alterations, you have to add authenticated users (or at least some group you are part of) to the share permissions (not ntfs) as it just adds creator owner. It also dosent add the deployment share path to bootstrip.ini (or is it customsettings.ini) so that when you pxe boot you have to type in the unc path (or edit the correct ini file before pxe booting) also deploying win10 it always seems to ask for a code (which on a vm network its never going to get) you can click go away but deployment waits for user input
Arthur Posted December 11, 2015 Posted December 11, 2015 (edited) a couple of issues ive found on a fresh install it creates the deploymentshare$ share with dumb permissions There's an easy fix for that (although it's annoying this bug exists in the first place)... http://deploymentresearch.com/Research/Post/518/Fixing-MDT-2013-Update-1-deployment-share-permissions-using-PowerShell # Check for elevation Write-Host "Checking for elevation" If (-NOT ([security.Principal.WindowsPrincipal] [security.Principal.WindowsIdentity]::GetCurrent()).IsInRole(` [security.Principal.WindowsBuiltInRole] "Administrator")) { Write-Warning "Oops, you need to run this script from an elevated PowerShell prompt!`nPlease start the PowerShell prompt as an Administrator and re-run the script." Write-Warning "Aborting script..." Break } # Configure NTFS Permissions for the MDT Build Lab deployment share $DeploymentShareNTFS = "E:\MDTBuildLab" icacls $DeploymentShareNTFS /grant '"Users":(OI)(CI)(RX)' icacls $DeploymentShareNTFS /grant '"Administrators":(OI)(CI)(F)' icacls $DeploymentShareNTFS /grant '"SYSTEM":(OI)(CI)(F)' icacls "$DeploymentShareNTFS\Captures" /grant '"VIAMONSTRA\MDT_BA":(OI)(CI)(M)' # Configure Sharing Permissions for the MDT Build Lab deployment share $DeploymentShare = "MDTBuildLab$" Grant-SmbShareAccess -Name $DeploymentShare -AccountName "EVERYONE" -AccessRight Change -Force Revoke-SmbShareAccess -Name $DeploymentShare -AccountName "CREATOR OWNER" -Force Edited December 11, 2015 by Arthur
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now