speckled

Check the required .net framework is installed, i had this exact issue, it turned out when i tested the manual install it worked because .net was installed on the test PC i was using but failed on other devices, when i checked the .net framework had not installed.

Because they can browse any of the folders and open any of the scripts they contain, the crux of it is i would rather the students not have the ability to search in the first place, that way the ability to do wrong is not removed.

the shares are secure, its the likes of netlogon and sysvol that worry me

So i have discovered that disabling cortana greys out the start menu for first use, clicking off and back on the menu resolves it. I have not found a fix for this so it looks like i either allow cortana and thus giving users the ability to UNC about the place or disable it and have the users live with the click. Anyone had this issue and found a fix for it?

You sir are a genius! first login now 40 seconds followed be 4 seconds for logins after that, now i just need to work out how to stop all the home folders displaying as documents.

Cheers bud, i will do that and give it a shot.

Yes i still use file screens to block these.

I was blocking the desktop.ini files on the server but as the profiles are now local it no longer applies.

So after quite some time i am eventually getting somewhere with W10, i am running 1803 i have tied it down nicely and got my start menu looking how i want it to now. There are however two problems i am now facing, and i dont seem to be able to resolve them no matter what i do: 1. First login takes almost 3 minutes, after that its down to 12 seconds 2. When i first click the start menu its greyed out and nothing is available, click off the menu and back on and its fine Anyone else having these issues or a workaround\fix for them?

I added the the credentials option and it did indeed work, strange how this worked in W7 though with the same scripts and account, the only change being the OS Thanks very much for your help with this problem.

its just referenced in the first file: Invoke-Command -ComputerName "WSH-SCCM-01" -FilePath "A:\Tools\PowershellScripts\Create-SCCMEntry.ps1" -ArgumentList $ComputerName,$MACAddress

i can run the called script manually fine, it seems to be how the script is called that is causing the issue, something must have change with W10 to cause this issue?

I have a problem running a powershell script since i moved to w10 as my workstation this is the script content: ###################################### # Script to prestage a computer in SCCM # Creates SCCM entry, puts it in the OSD collection # and then creates an AD account and puts # it in the Test OU. ###################################### param ( [parameter(ValueFromPipelineByPropertyName,Mandatory)] [Alias('Computer Name','Computer','Device','Device Name','Name')] [string]$ComputerName, [parameter(ValueFromPipelineByPropertyName,Mandatory)] [validateScript({ if ($_ -match '^([0-9A-F]{2}[:-]){5}([0-9A-F]{2})$') { $True } else { Throw "$_ is not a valid MAC Address." } })] [Alias('MAC')] [string]$MACAddress ) Process { $ComputerName = $ComputerName.ToUpper() $MACAddress = $MACAddress.ToUpper() $ValidateComputerName = $ComputerName.Split("-") if ($ValidateComputerName.Count -eq 3) { if ($ValidateComputerName[0] -notmatch "WSH" -or $ValidateComputerName[2] -notmatch "^[TD\d]+$") { Write-Host "This isn't a valid computer name" Exit } } else { Write-Host "This isn't a valid computer name" Exit } Invoke-Command -ComputerName "WSH-SCCM-01" -FilePath "A:\Tools\PowershellScripts\Create-SCCMEntry.ps1" -ArgumentList $ComputerName,$MACAddress New-ADComputer -Name $ComputerName -SamAccountName $ComputerName -Enabled:$True } the script ic calls is this: param ( [string]$ComputerName = $(Read-Host "Enter a computer name"), [string]$MACAddress = $(Read-Host "Enter a MAC Address") ) Import-Module 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\ConfigurationManager.psd1' Set-Location WSH: Import-CMComputerInformation -CollectionName "Windows 7 Clients" -ComputerName $ComputerName -MacAddress $MACAddress #Get-CMDevice -Name $ComputerName | Foreach {Add-CMDeviceCollectionDirectMembershipRule -Collection "Windows 7 Clients" -ResourceId $_.ResourceID} start-sleep -seconds 5 #Invoke-CMDeviceCollectionUpdate -Name "Deployment Test" Invoke-CMDeviceCollectionUpdate -Name "Windows 7 Clients" and this is the error i get when i run the script: Cannot find drive. A drive with the name 'WSH' does not exist. + CategoryInfo : ObjectNotFound: (WSH:String) [set-Location], DriveNotFoundException + FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.SetLocationCommand + PSComputerName : WSH-SCCM-01 This command cannot be run from the current drive. To run this command you must first connect to a Configuration Manager drive. + CategoryInfo : DeviceError: (Microsoft.Confi...ormationCommand:ImportComputerInformationCommand) [impor t-CMComputerInformation], InvalidOperationException + FullyQualifiedErrorId : CommandCannotExecuteFromCurrentDrive,Microsoft.ConfigurationManagement.Cmdlets.Oob.Comma nds.ImportComputerInformationCommand + PSComputerName : WSH-SCCM-01 I have been battling with this for quite some time and dont seem to be making any progress, any help would be appreciated.

Hi pal, Basically it was a problem with O365, I logged a call with Microsoft through the portal and they resolved the issue working with me over 2 days.

I didnt, but i just validated it there using an online validator and it didnt flag anything up, good trick to know though cheers.