There are three main steps to complete this rather difficult task:
– Setup Hyper-V Server 2012 R2 to accept connections
– Setup Remote Server Management on desktop machine
– Setup Hyper-V Management on desktop machine
For the detailed step see:
Ben Armstrong’s Virtualization Blog – Configuring Remote Management of Hyper-V Server – in a Workgroup
Public Jotting – Hyper-V Server 2012 and remote hyper-v management in a workgroup (on windows 8 client)
Nearly Deaf – Setting up Windows Hyper-V Server 2012 R2 in a workgroup
Office 365 Top Resources for Partners
Just install the Configuration Manager client on a workgroup machine. Here are the steps I followed:
- Create and import a local computer PFX file for the workgroup machine
- Export then Import the Root Certificate
- Navigate to the share: \\server\sms_pri\client
- The client must be manually installed on each workgroup computer. Run the install command: ccmsetup.exe /UsePKICert /NoCRLCheck SMSMP=HTTPS://server.domain.net SMSSITECODE=A01 DNSSUFFIX=domain.net SMSSLP=HTTPS://server.domain.net
- Approve the client in the Configuration Manager console
- Workgroup clients cannot locate their default management point from Active Directory
- Active Directory discovery methods will not discover computers in workgroups
- Advertisements targeted to users are not possible
For more good info see Chris Sugdinis’s post, Peter van der Woude post regarding certificate creation and of course the TechNet site.
Making a MDT Lite-Touch connect to the Deployment Share can be done automatically. Just enter the credentials in the bootstrap.ini file.
For Workgroup machines use the appropriate local account.
The UserDomain syntax can be dropped.