 
      
    | You are here | adsecurity.org | ||
| | | | | oofhours.com | |
| | | | | As some of you have noticed, the naming convention allowed for Windows Autopilot Hybrid Azure AD joined devices isn't particularly flexible: You can specify a prefix (e.g. "AD-") and the rest of the computer name will be filled in with random characters and digits to pad the name to 15 characters. So you end up... | |
| | | | | o365blog.com | |
| | | | | The toolkit for Azure AD hackers, bounty hunters, red/blue teamers | |
| | | | | aadinternals.com | |
| | | | | The toolkit for Azure AD hackers, bounty hunters, red/blue teamers | |
| | | | | smsagent.blog | |
| | | For some time I've used a simple VBScript wrapper in code projects and scheduled tasks to allow silent execution of PowerShell scripts in the user context without displaying a console window: p = CreateObject("Scripting.FileSystemObject").GetParentFolderName(WScript.ScriptFullName) location = p &"\"& WScript.Arguments(0) command = "powershell.exe -nologo -ExecutionPolicy Bypass -File """ &location &"""" set shell = CreateObject("WScript.Shell") shell.Run command,0... | ||