Remote management policy

Hi we're having an issue ever since our Windows Server 2008 ZCM server was updated from 11.1 to 11.2.
It looks like the remote management policy that we typically use no longer is effective.
The original policy was setup in a way that you did not have to require users consent to remote the machine. Now it does. When I do a properties on the agent in the remote management policy section, it shows up as recognizing only the default.
Any ideas?

sflegnc,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Similar Messages

ZCM 11 Remote Management Policy Failed after Patch 2

Upgraded to Cumulative Agent Patch 2 on ZCM 11 and now my remote management policy fails. It keeps stating that it "Could not find a results file for remote management policy...."
Is anyone else having this issue?

Dpogue,
This is being worked on, it's not related to the agent update as far as
we know - TID 7006354 has some details.
Shaun Pond

Schema entry for Remote Management Policy

Does anybody know the schema entry for Remote Management Policy in a user
object? Specifically the entry that says "Use These Settings and Ignore
Remote Management Policy"?
Thanks!
Mike

On Wed, 20 Apr 2005 18:57:10 GMT, [email protected] wrote:
> Does anybody know the schema entry for Remote Management Policy in a user
> object? Specifically the entry that says "Use These Settings and Ignore
> Remote Management Policy"?
console one could tell you..
Marcus Breiden
Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

How to use VNC-Client or sim. for remote management

Hi folks,
how can i use a VNC-Client to do a remote session with a ZCM10 RM-enabled
client ?
Any ideas ?
Regards
Thorsten

thanks !!1
>>> Michael Fleming<[email protected]> schrieb am
Dienstag, 11. Januar 2011 um 14:06 in Nachricht
<[email protected]>:
> After you have set a Remote Management Policy (with VNC password) and
> assigned to the device, then run %appdata%\novell\ZENworks\Remote
> Management\bin\nzrViewer.exe. Put in device IP/DNS ~50. Done.

Can't find "Windows Remote Management (WinRM)" in Group Policy Management console

So looking at different scenarios for enabling WinRM / PSRemote. Find all kinds of information on how to do it... stoked right!? Not so much, I can't find Windows Remote Management (WinRM) where it should be, or anywhere else. WTF? Any ideas here kids?And
OBTW, Domain Functional Level is 2008 R2 with Windows 2012 R2 DC's.

Oh man, found the answer... Doh!
Run from an elevated command prompt;
robocopy "%windir%\policydefinitions" "\\%userdnsdomain%\sysvol\%userdnsdomain%\policies\policydefinitions" /s
So there you go.

Windows Server 2008 - How to remotely manage account passwords?

I'm hoping to get direction on how to remotely manage 'user accounts' on Windows Server 2008 machines. The remote management would be from an automated perspective. For example, I have a custom application (maybe C#, Java, etc) that runs on one
server that makes connections to various 'Windows Server 2008' servers; and I want it to be able to do the following.
Query Windows Server 2008 box for full list of user accounts
Update password for user account
Lock account
Unlock account
Check policy information to find out when password may expire
I'm trying to find out what may already be available and running on Windows Server 2008 that I can take advantage to get this done programmatically.
-Wes

I agree with Mekac, the gallery should provide a lot of script of what you want to do.
Like ;
https://gallery.technet.microsoft.com/Password-Expiry-Email-177c3e27 - Password Expiry Email Notification.
Regards, Philippe
Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!

Error 1853 /RCAICIP.HST/ Zenworks 7 remote management

I am getting an error 1853 when I try to remote manage/view some
workstation. Another workstation i can manage normally.
Here is the log:
#(160)# 7:42:35 08/17/07 Normal : Resource DLL is successfully loaded
#(160)# 7:42:35 08/17/07 Normal : Reading settings from the file
#(160)# 7:42:35 08/17/07 Normal : C:\Program
Files\Novell\ZENworks\RemoteManagement\RMAgent\RMC FG.INI
#(160)# 7:42:35 08/17/07 Normal : Port value read from file = 1761 and
it will be used as the RM Communication port
#(160)# 7:42:35 08/17/07 Normal : Loading : C:\Program
Files\Novell\ZENworks\ZenLite.dll
#(160)# 7:42:35 08/17/07 Normal : Loading : C:\Program
Files\Novell\ZENworks\ZenPol32.dll
#(160)# 7:42:35 08/17/07 Normal : ZENNDSUtil: Successfully loaded
dependent modules...
#(160)# 7:42:35 08/17/07 Normal : LoadZenAutilLibraryAndGetProc:
Successfully loaded ZenAutil.dll and its dependent DLLs
#(160)# 7:42:35 08/17/07 Normal : ZenRem32.exe : ZenRem32ServiceMain()
successfully loaded Zenlite DLL
#(160)# 7:42:43 08/17/07 Normal : IsOsServer() : MyNetServerGetInfo
value of pServerInfo = 1002
#(160)# 7:42:43 08/17/07 Critical : Failed to write the header
information in RCAICIP.HST GetLastError(): 6
#(160)# 7:42:43 08/17/07 Normal : ZENNDSUtil: Attempting to read
policies...
#(160)# 7:42:43 08/17/07 Normal : ZENUtil: ZENIsWorkstationRegistered:
wsDN =
#(160)# 7:42:43 08/17/07 Normal : Workstation is registered
#(160)# 7:42:43 08/17/07 Normal : Reading workstation DN and tree
name...
#(160)# 7:42:43 08/17/07 Normal : workstation DN - CN=
#(160)# 7:42:43 08/17/07 Normal : Loading : C:\Program
Files\Novell\ZENworks\WMSchApi.dll
#(160)# 7:42:43 08/17/07 Critical : WMIsWorkstationAuthenticated
failed. errorCode: 1062
#(160)# 7:42:48 08/17/07 Normal : Workstation IS authenticated...
#(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Loaded [ZENNW32.DLL]
successfully
#(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Successfully initialized
context
#(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Failure in reading
boolean attribute DM:Ignore Policy in CN=
#(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Workstation Policy -
'Workstation Package:Windows XP:Remote Control Policy.'
#(160)# 7:42:48 08/17/07 Normal : Reading workstation DN and tree
name...
#(160)# 7:42:48 08/17/07 Normal : workstation DN - CN=
#(160)# 7:42:48 08/17/07 Normal : Loading : C:\Program
Files\Novell\ZENworks\WMSchApi.dll
#(160)# 7:42:48 08/17/07 Normal : Workstation IS authenticated...
#(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Loaded [ZENNW32.DLL]
successfully
#(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Successfully initialized
context
#(160)# 7:42:48 08/17/07 Normal : Failed to open
HKLM\Software\Novell\ZENWorks\CurrentUserDN
#(160)# 7:42:48 08/17/07 Normal : Only workstation policy settings
active...
#(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Finished reading
policies
#(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Unloaded modules...
#(160)# 7:42:48 08/17/07 Normal : UnLoadZenAutilLibrary :Successfully
unloaded ZenAutil.dll
Any help or suggestions would appreciated,
Thanks,
Lubos.
fool01

I'm getting the same error. In my situation all of the machines are
together on 2 different switches. I wonder if it is possibly a
network issue?
On Fri, 17 Aug 2007 11:59:22 +0000, fool01 wrote:
>
> I am getting an error 1853 when I try to remote manage/view some
> workstation. Another workstation i can manage normally.
>
> Here is the log:
> #(160)# 7:42:35 08/17/07 Normal : Resource DLL is successfully loaded
> #(160)# 7:42:35 08/17/07 Normal : Reading settings from the file
> #(160)# 7:42:35 08/17/07 Normal : C:\Program
> Files\Novell\ZENworks\RemoteManagement\RMAgent\RMC FG.INI
> #(160)# 7:42:35 08/17/07 Normal : Port value read from file = 1761 and
> it will be used as the RM Communication port
> #(160)# 7:42:35 08/17/07 Normal : Loading : C:\Program
> Files\Novell\ZENworks\ZenLite.dll
> #(160)# 7:42:35 08/17/07 Normal : Loading : C:\Program
> Files\Novell\ZENworks\ZenPol32.dll
> #(160)# 7:42:35 08/17/07 Normal : ZENNDSUtil: Successfully loaded
> dependent modules...
> #(160)# 7:42:35 08/17/07 Normal : LoadZenAutilLibraryAndGetProc:
> Successfully loaded ZenAutil.dll and its dependent DLLs
> #(160)# 7:42:35 08/17/07 Normal : ZenRem32.exe : ZenRem32ServiceMain()
> successfully loaded Zenlite DLL
> #(160)# 7:42:43 08/17/07 Normal : IsOsServer() : MyNetServerGetInfo
> value of pServerInfo = 1002
> #(160)# 7:42:43 08/17/07 Critical : Failed to write the header
> information in RCAICIP.HST GetLastError(): 6
> #(160)# 7:42:43 08/17/07 Normal : ZENNDSUtil: Attempting to read
> policies...
> #(160)# 7:42:43 08/17/07 Normal : ZENUtil: ZENIsWorkstationRegistered:
> wsDN =
> #(160)# 7:42:43 08/17/07 Normal : Workstation is registered
> #(160)# 7:42:43 08/17/07 Normal : Reading workstation DN and tree
> name...
> #(160)# 7:42:43 08/17/07 Normal : workstation DN - CN=
> #(160)# 7:42:43 08/17/07 Normal : Loading : C:\Program
> Files\Novell\ZENworks\WMSchApi.dll
> #(160)# 7:42:43 08/17/07 Critical : WMIsWorkstationAuthenticated
> failed. errorCode: 1062
> #(160)# 7:42:48 08/17/07 Normal : Workstation IS authenticated...
> #(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Loaded [ZENNW32.DLL]
> successfully
> #(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Successfully initialized
> context
> #(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Failure in reading
> boolean attribute DM:Ignore Policy in CN=
> #(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Workstation Policy -
> 'Workstation Package:Windows XP:Remote Control Policy.'
> #(160)# 7:42:48 08/17/07 Normal : Reading workstation DN and tree
> name...
> #(160)# 7:42:48 08/17/07 Normal : workstation DN - CN=
> #(160)# 7:42:48 08/17/07 Normal : Loading : C:\Program
> Files\Novell\ZENworks\WMSchApi.dll
> #(160)# 7:42:48 08/17/07 Normal : Workstation IS authenticated...
> #(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Loaded [ZENNW32.DLL]
> successfully
> #(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Successfully initialized
> context
> #(160)# 7:42:48 08/17/07 Normal : Failed to open
> HKLM\Software\Novell\ZENWorks\CurrentUserDN
> #(160)# 7:42:48 08/17/07 Normal : Only workstation policy settings
> active...
> #(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Finished reading
> policies
> #(160)# 7:42:48 08/17/07 Normal : ZENNDSUtil: Unloaded modules...
> #(160)# 7:42:48 08/17/07 Normal : UnLoadZenAutilLibrary :Successfully
> unloaded ZenAutil.dll
>
>
> Any help or suggestions would appreciated,
>
> Thanks,
>
> Lubos.

Effective Rights for Remote Management

How are an Administrator's Remote Management rights determined with regard to devices and users?
If an Administrator has Remote Control rights to a device, should they be able to remote control that device no matter what user is logged into it?
Conversely, if an Administrator has Remote Control rights to a user, should they be able to remote control that user no matter what device the user is logged into?
Thanks.

Michelsr,
it's the most restrictive combination that's effective - allowing
things like:
1) you have a device policy that says "allow", but the CEO logins in
and his policy is set to "deny", then you cannot remote control him
2) you have machines that contain sensitive information, so they have a
policy that says "deny", and a user logs in that has a policy that says
"allow", you cannot access that session.
Shaun Pond

Remote Management - 1855

Hi
ZDM65SP1 environment, MS/Agent only with middle tier. Trying to r/c a
machine that has sucessfully registered accross and firewall with single
NAT (have enabled NAT in r/c policy!)
Keep getting '1855 - Unable to continue with Remote Management Session...'
The COnsoleOne error log shows:
#(2904)# 19:00:48 08/23/05 Normal : CONSOLE > Resource is loaded successfully
#(2904)# 19:00:48 08/23/05 Normal : CONSOLE > Inside LoadandParseCommand
#(2904)# 19:00:48 08/23/05 NORMAL : CONSOLE > AppData.bSessionRestart ==
FALSE Hiding window
#(2904)# 19:00:48 08/23/05 NORMAL : CONSOLE > Command line parameters
parsed successfully
#(2904)# 19:01:09 08/23/05 Critical : InitClient failed due to Connect()
function ZENCOMM_FAILURE
#(2904)# 19:01:09 08/23/05 NORMAL : InitClientInLoop() failed. Trying 1761...
So it looks like it could be a firewall/port issue, though the network guys
assure me that 1761 and 1762 are open on both firewalls....
I can get a session if the wstn initiates the request, and enters the NAT
of the mgmt console (zen server)
Any suggestions?
Cheers
David

On Tue, 23 Aug 2005 18:05:28 GMT, [email protected]
wrote:
> Any suggestions?
how is your network set up?
dynamic nat only allows outgoing sessions... looks like you are at the
public side of the nat...
Marcus Breiden
Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

1456: The remote management agent is unable

Hi
I have :
Server NW6.5 Sp5
Zenworks desktop 6.5 SP2
Client NT4 SP6 - Client novell 4.90 SP2
W2000 SP4 - Client novell 4.91 SP2 - Agent Zen SP2
WXP SP2 - Client novell 4.91 SP2 - Agent Zen SP2
The problem is that I can't connet with "remote management" some PC with XP;
The error in log file is:
#(464)# 10.16.27 02/16/06 Normal : Loading :
C:\Programmi\Novell\ZENworks\WMSchApi.dll
#(464)# 10.16.27 02/16/06 Critical : Workstation NOT yet authenticated...
#(464)# 10.16.27 02/16/06 Critical : ZENNDSUtil: initializeContext()
failed...
#(464)# 10.16.27 02/16/06 Normal : Reading workstation DN and tree name...
#(464)# 10.16.27 02/16/06 Normal : workstation DN -
PC01-WINXP-00:0B:CD:F8:F2:44., treename - TREE_GROUP
#(464)# 10.16.27 02/16/06 Normal : Loading :
C:\Programmi\Novell\ZENworks\WMSchApi.dll
#(464)# 10.16.27 02/16/06 Critical : Workstation NOT yet authenticated...
#(464)# 10.16.27 02/16/06 Critical : ZENNDSUtil: initializeContext()
failed...
#(464)# 10.16.27 02/16/06 Normal : Neither policy settings active. All
operations disabled.
#(464)# 10.16.27 02/16/06 Normal : ZENNDSUtil: Finished reading policies
#(464)# 10.16.27 02/16/06 Normal : ZENNDSUtil: Unloaded modules...
#(464)# 10.16.27 02/16/06 Normal : UnLoadZenAutilLibrary :Successfully
unloaded ZenAutil.dll
#(464)# 10.17.48 02/16/06 Normal : RMSessionFinished - Begin
If I check if the ogject workstation is authenticated on NDS, I not find the
connection.
I can connect only with che workstation that are list in connection.
Why some workstation connect to NDS ?
Thanks for help.
Gianluigi

Try deleting the workstation object and reboot the workstation (sometimes
a 2nd reboot is required).
> Hi
>
> Another information, if I use only the agent with out client novell, I
have
> no problem because the workstation is connect to NDS.
> If I want use client novell and Middle Tier is possible set Middle Tier
how
> default connection for remote manager ?
>
> Thank
>
> Gianluigi
>
> "Gianluigi Cortinovis" <[email protected]> ha scritto nel messaggio
> news:[email protected]...
> > No, I have disable windows firewall.
> >
> > Gianluigi
> >
> > "craig wilson" <[email protected]> ha scritto nel messaggio
> > news:[email protected]...
> >> Windows Firewall perhaps?
> >>
> >> --
> >> Craig Wilson
> >> Novell Product Support Forum Sysop
> >> Master CNE, MCSE 2003, CCNA
> >>
> >> Editor - http://www.ithowto.com
> >>
> >> (Seeking Full-Time Expert? Drop me a note :> )
> >>
> >>
> >> "Gianluigi Cortinovis" <[email protected]> wrote in message
> >> news:[email protected]...
> >>> Hi
> >>>
> >>> I have :
> >>> Server NW6.5 Sp5
> >>> Zenworks desktop 6.5 SP2
> >>>
> >>> Client NT4 SP6 - Client novell 4.90 SP2
> >>> W2000 SP4 - Client novell 4.91 SP2 - Agent Zen SP2
> >>> WXP SP2 - Client novell 4.91 SP2 - Agent Zen SP2
> >>>
> >>>
> >>> The problem is that I can't connet with "remote management" some PC
with
> >>> XP;
> >>> The error in log file is:
> >>>
> >>> #(464)# 10.16.27 02/16/06 Normal : Loading :
> >>> C:\Programmi\Novell\ZENworks\WMSchApi.dll
> >>> #(464)# 10.16.27 02/16/06 Critical : Workstation NOT yet
> >>> authenticated...
> >>> #(464)# 10.16.27 02/16/06 Critical : ZENNDSUtil: initializeContext
> >>> failed...
> >>> #(464)# 10.16.27 02/16/06 Normal : Reading workstation DN and tree
> >>> name...
> >>> #(464)# 10.16.27 02/16/06 Normal : workstation DN -
> >>> PC01-WINXP-00:0B:CD:F8:F2:44., treename - TREE_GROUP
> >>> #(464)# 10.16.27 02/16/06 Normal : Loading :
> >>> C:\Programmi\Novell\ZENworks\WMSchApi.dll
> >>> *******************************************
> >>> #(464)# 10.16.27 02/16/06 Critical : Workstation NOT yet
> >>> authenticated...
> >>> #(464)# 10.16.27 02/16/06 Critical : ZENNDSUtil: initializeContext
> >>> failed...
> >>> *******************************************
> >>> #(464)# 10.16.27 02/16/06 Normal : Neither policy settings active.
All
> >>> operations disabled.
> >>> #(464)# 10.16.27 02/16/06 Normal : ZENNDSUtil: Finished reading
policies
> >>> #(464)# 10.16.27 02/16/06 Normal : ZENNDSUtil: Unloaded modules...
> >>> #(464)# 10.16.27 02/16/06 Normal :
UnLoadZenAutilLibrary :Successfully
> >>> unloaded ZenAutil.dll
> >>> #(464)# 10.17.48 02/16/06 Normal : RMSessionFinished - Begin
> >>>
> >>>
> >>> If I check if the ogject workstation is authenticated on NDS, I not
find
> >>> the connection.
> >>>
> >>> I can connect only with che workstation that are list in connection.
> >>>
> >>> Why some workstation connect to NDS ?
> >>>
> >>> Thanks for help.
> >>>
> >>> Gianluigi
> >>>
> >>>
> >>
> >>
> >
> >
>
>

How to enable remote management on a remote computer

Hi!
I have some problems with this.
I need to enable remotely the feature for remote management, i have a test scenario with one server 2008 r2 and one server 2012 r2, and i need to sends scripts remotely from server 2012 to server 2008 and i need to do this several times on multiple servers.
Can anyone help?
Thanks

Hi,
Group Policy is the best way to configure PowerShell remoting, but you can try this:
https://gallery.technet.microsoft.com/scriptcenter/Enable-PSRemoting-Remotely-6cedfcb0
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

Guide to remote manage Hyper-V servers and VM's in workgroups or standalone

This guide is based on the following 3 products:
Windows server 2012 (core)
Windows 8
Hyper-V server v3 / Hyper-V server 2012
The following guide will enable you to:
1: remotely manage your Hyper-V Virtual Machines with Hyper-V manager
2: remotely manage your Hyper-V servers' firewall with a MMC snap-in.
3: remotely manage your Hyper-V server (2012) with server manager
! This should also work for Core installations of server 2012, but I haven't tried.
This guide is purely focussed on servers in a WORKGROUP, or as a stand alone.
I CAN NOT tell you what you need to do to get it working in a domain.
* You can run these commands straight from the console (Physically at the machine) or through RDP.
* You will need to be logged on as an administrator.
* Commands are listed in somewhat random order; I do however advise to follow the steps as listed.
* Commands with ? in front of them are only ment to be helpfull for troubleshooting,
* and to identify settings and changes made.
* Commands and instructions with ! in front of them are mandatory.
- server: means the server core or hyper-v server (non gui)
- client: means the machine you want to use for remote administration.
- Some commands are spread over 2 lines; be sure to copy the full syntax.
> To enable the Hyper-V manager to connect to your server, you need to perform the following 2 actions: (Assuming you have already installed the feature)
1:
! Client: Locate the C:\Windows\System32\Drivers\etc\hosts file.
! right-click --> properties --> security
! click --> edit --> add --> YOURUSERNAME or Administrator --> OK
! then select this new user, and tick the "modify"-box under the "allow"-section.
! apply the change, and close.
! doubleclick the file, and open with notepad
! add the ip-address and name of your server (no // or other crap needed)
! Save the file
# I recommend putting a shortcut to this file on the desktop.
# If you change the ip-address of your server (e.g. move the server from staging to a live environment)
# you might forget to do so in the hosts file.
# Hyper-V manager, MMC, RSAT, and Server-manager all rely on the hosts-file to resolve the name.
# some of these might connect to their respective service on an i.p.-level, but some don't.
# This is the main reason you need to modify this file.
! USE AN ELEVATED CMD/POWERSHELL PROMPT TO CONTINUE !
# the next config needs to be done on windows 8.
# It seems that it's already preconfigured under server 2012
2:
! Client: dcomcnfg
! open component services --> computers
! right-click -> my computer -> properties
! select "COM SECURITY" tab
! under "ACCESS PERMISSIONS" select "edit limits"
! select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
# Without this adjustment, you can't connect to your Hyper-V server
# with the Hyper-V manager if you're not in a domain.
> And if you haven't done so already... make sure you have enabled remote management number 4 on the Hyper-V server console.
> Next, is to get the MMC firewall snap-in working.
The reason for this, is to have a GUI available to configure it.
If you're happy without it, you may skip this and use a shell instead to do so.
? server: netsh advfirewall show currentprofile
# shows the current profile (public/domain/private) and its settings
# depending on your needs, you should set the right profile to fit your needs.
# You can easily do this when the MMC snap-in is done. (after you've followed these steps)
! server: netsh advfirewall set currentprofile settings remotemanagement enable
# enables remote management of the firewall on an application level
# (In other words: allows the firewall to be remotely managed)
! server: netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
# allows remote management of the firewall, through the required firewall ports with TCP protocol.
# 4 rules will be updated to allow access: public & Domain, dynamic and endpoint-mapper.
# You can disable/add/change the rule from the MMC snap-in after finishing this guide.
# e.g. set the firewall through the MMC-GUI to only allow specific ip-addresses etc.
? server: netsh advfirewall firewall show rule all
# Shows a list of available rules, and their current state.
# when run from cmd, the list exceeds the maximum length for review.
# (from cmd,type:) start powershell, and run the command from there.
! Client: cmdkey /add:YOURSERVERNAME /user:USERNAMEONTHESERVER /pass:THEPASSWORDOFTHATUSER
# I recommend you to use a username with enough privileges for management
# All capital letters need to be replaced with your input
# CMD answers "credential added successfully" when you're done
! Client: locate MMC, and run it as an admin.
# In windows 8/2012, go to search and type MMC. Right-click the icon,
# and choose run as admin on the bar below.
! Client: application MMC: select "file" --> Add/remove snap-in
! --> (left pane) scroll down to "windows firewall" --> select and click "add"
! select "another computer"
! type the name of the server you want to manage (NO workgroup/ or //, just same name as you typed for cmdkey)
* Part 2 is done.
# Have a look by doubleclicking the firewall icon in the left pane.
# It looks and works the same as the GUI version that you are familiar with.
! Next is the Server Manager.
# Follow the steps listed to get your server listed and manageable in the server manager.
! Client: Open the created Firewall snap-in for your server.
! Find the 3 "Remote Event Log Management" entries in the list of INBOUND rules, and enable them.
! Open powershell --> in cmd windows, type: start powershell
! run the following line in powershell
! Client: in C:\Windows\system32> set-item WSMAN:\localhost\client\trustedhosts -value YOURSERVERNAME -concatenate
# WinRM Security Configuration.
# This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
# authenticated. The client might send credential information to these computers. Are you sure that you want to modify
# this list?
# [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
# I recommend to choose yes; unless you like to pull some more hairs...
! server: winrm qc
# WinRM service is already running on this machine.
# WinRM is not set up to allow remote access to this machine for management.
# The following changes must be made:
# Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely
# to local users.
# Make the changes? y / n
! select yes
! Client: open the server 2012 server manager
! click manage -> add server
! select the DNS tab, and type the name of your server
Done.
You can now manage your remote server through the familiar computer management GUI.
! Right-click your remote server, and select "Computer Management"
A few side notes:
? The Performance tab seems to list the local machine's performance, in stead of the remote servers'
? If you want Windows server backup, you need to right-click the server in the server manager, and select "add roles and features.
? it will then become available under the "computer management" of the remote server.
If you liked this guide you may thank my employer, Mr. Chris W.
for giving me the time to work it all out.
Cheers!

As a little update to the post, I'd like to add that replication, clustering and migration will not work in workgroup environments. Unless someone can provide an additional guide for this, I'd recommend anyone to no even bother to try.
To manage the standalone hyper-v server in a remote location over the internet, I would recommend the following:
Install windows 8 pro (x86 uses less resources!) as a vm on the host, and assign 2 network connections to it.
1 external (shared with host) (be sure you have a dedicated ip-address for it!)
1 internal connection.
What I did was this:
As soon as you've installed the win8 guest, proceed with the guide as described.
For the 1st step of the guide (hosts-file) use the ip-address you will later assign to the "internal" network switch of the host!
In my example, I'm using 10.0.0.1 for the host, and 10.0.0.2 for the guest.
To be clear: I first used the guide on a LAN-environment, and did all the steps from a "real" client to server on the LAN.
Then, installed the win8 guest on the host using the "real" clients' hyper-v manager over the LAN.
Next, assigned the 2 network connections to the VM, and configured them as follows:
external - as you would to be able to make your guest reach the internet.
internal - I used the following config:
ip-address: 10.0.0.2
subnet: 255.255.255.252
gateway - blank
dns - Blank
Now, when you get to the console of the hyper-v server (host) or RDP to it, go to network settings.
You'll see that the internal card has been added here as well.
Configure it as follows:
ip-address: static - 10.0.0.1
subnet: 255.255.255.252
gateway - blank
dns - blank
You should now be able to ping your guest (win8) on 10.0.0.2 if it's running.
Don't forget to enable ping response (option 4 on the host) to test connectivity the other way around as well (guest to host)
When you're done, you'll be able to RDP to the guest OS over the internet, and then connect to the host with server manager, hyper-v manager, and MMC.
Don't forget to enable each module on the hosts' firewall to make the snap-ins work!
Remote volume management requires your guest/client firewall INcoming ports to be enabled as well! not just the host.
Either update the firewall rules from the MMC gui as described in the guide, or use the following commands on the
hosts' powershell:
Enable the firewall rules with the command Enable-NetFirewallRule -DisplayGroup "USE_THE_COMMANDS_BELOW" (include the " " in the command)
Remote Service Management
Remote Volume Management
Remote Event Log Management
Remote Scheduled Tasks Management
Windows Firewall Remote Management
Windows Remote Management
You can get the list with Get-NetFirewallRule -DisplayName *management*
You can get the list with Get-NetFirewallRule -DisplayName *remote*
Commands provided with credits to F. verstegen
Cheers,
Michael.
Sigh...

How can i prevent users to delete remote management on their IPADs

hello everyone
i have Mac with OS X server i have created profile manager to manage the students I Pad's
students keep deleting the profile remote management profile
anyway to help me to manage their I PADS remotely

When configuring a profile in Profile Manager, if you edit the General entry you can set it to require a password before allowing a user to remove the profile. If you don't give users this password then they will not be able to remove it.

Screen sharing and remote management no longer working after some uptime

Server is withoiut monitor.
Users need to login via screen sharing from time to time.
"Enable screen sharing and remote management" is ticked in Server.app everything is working fine (for days, weeks).
ARD reports "Screen Sharing Available", so remote management is not running how it should.
Screen Sharing.app is "Connecting…" forever.
Kickstarting ARD (http://support.apple.com/kb/HT2370) does not help.
Restart fixes it.
Is there a workaround (over ssh) or a fix?

seduc wrote:
Do you know if
fdesetup authrestart
works then too?
Off-hand, no. I don't. See this posting, or as would be typical in any case, try it?

Screen Sharing and Remote Management

Is there a way in 10.6 to make both Screen Sharing and Remote Management run at the same time?
In the past (10.5), you could convince Mac OS to run both Screen Sharing and Remote Management to run simultaneously. I say "convince" because you could not enable them both through System Preferences. You could turn one on, then use Terminal to enable the other. This worked great for me, because I needed remote management for the machines I managed, and the users need screen sharing to work from home.
However, the work-around for 10.5 no longer seems to work for 10.6. Has any one gotten this to work yet for 10.6? Thanks!

I figured this out. First enable Remote Management via System Preferences. Then create /private/etc/ScreenSharing.launchd with 'enabled' as it's contents.

Remote management policy

Similar Messages

Maybe you are looking for