Remote Management settings

I am trying to turn on my screen sharing but when I go to the system preferences "Sharing" tab, and click on the "Screen Sharing" and the message "Screen Sharing is currently being controlled by the Remote Management service". I naturally go to the remote management tab, but it is not there. Any help?
I am using a late 2010 MBA

If your users have local administrator privileges, there's no way I know of to totally prevent them from being able to alter the settings. You can, if you're using Managed Preferences from Mac OS X Server, turn off access to the Sharing control panel, I believe, but that won't stop a knowledgeable user from just using the kickstart command to alter the ARD settings or turn the ARD client off again.

Similar Messages

Default Remote Management Settings

I just (for the first time ever) looked at my Remote Management settings and VNC access was turned on and Show status in menu bar was turned off. That seems a bit precarious and unorthodox.
Is that the default setting or has my system been changed by someone/thing? Is there a way to easily parse my secure.log (i.e., a useful string to search for) that would tell me if I have had unauthorized connections?

Try the following steps:
A] With the help of Cisco Connect Software (if at all you have installed the router with the help of this software)
1] Open the software and go to the option which says "Router Settings"
2] Then click on the option which says "Advanced Settings" which will take you to the router's configuration page.
3] Then click on Security tab disable SPI Firewall Protection, uncheck Filter Anonymous Internet Requests...
B] If you haven't installed Cisco Connect then you can log on to the router's user interface using it's default IP address in the browser which is 192.168.1.1 and type in 'admin' as the password leaving the username field blank. This will take you to the router's web interface and then follow steps as mentioned above to make the changes.

Changed Remote Management Settings -- Lost ARD Control!

I run a headless server. My remote management settings on the server were set to allow "all users" to control it. I changed it to allow "only these users" and it was set to the current and only user "admin". I immediately lost control of the server in ARD. When I try to re-add it to my list, it accepts "admin" and the password but refuses to allow me to control the server anymiore.
Needless to say: Help!

well, that was exciting . . . i was able to login as the superuser (root).
what's interesting is that when i re-established contact with the server the remote management/options window was open and none of the boxes were checked.
since it limited control to the admin user immediately upon selecting it, therefore, it stopped allowing me to control it via ARD. not sure how one could set control the admin only on a headless server, but all's well that ends well.

How to manage Remote Management settings with Snow Leopard Server

At my business, I manage our Macs' preferences using Managed Client as part of Mac OS X Server 10.6... one thing I have not been able to figure out is how to enforce settings for Remote Management. For example: I want only the administrator user to be able to control a machine, and only run reports but not copy software, etc.
I have tried configuring a machine correctly, then importing com.apple.RemoteManagement.plist and com.apple.ARDAgent.plist into Workgroup Manager. No luck. I wonder if anyone out there has solved a similar problem.

Open the Server Admin program (in the dock if nowhere else). It's there.

Changed Remote Management settings, now I can't authenticate!

I recently changed some settings on several machines at my workplace, and one of the settings was to allow all accounts, and not just the previously existing accounts, to access some computers using Remote Management.
I didn't turn Remote Management off, I just changed it from "Allow access for: Only these users:" to "Allow access for: All users". The host machine has 10.6.3 and ARD 3.3.2. All the clients have either 10.6.3 or 10.5.8. Any machines that I haven't changed that setting for work great, and I am able to authenticate, just the ones that I have changed their settings.
I have noticed that when I use an account that is valid on that machine, it colors the icon as if I had put a proper username/password in. I have tried new preference files, I have done the "kickstart" processes, and I have tried ScreenSharing.app, and none of them work. I have tried ScreenSharing.app from other computers, and it fails as well, telling me the problem is with the affected client computers, and not the host.
Any help would be much appreciated.

Okay, I just had an "oh yeah!" moment where it suddenly dawned on me; when I change from "Only these users:" to "All users", I need to adjust the Options... settings to allow for users to remotely connect again.

Blocking rights to change Remote Management Settings

I'm in a school system, and we're getting ZW 7 set up. I have a couple
of users per school who have rights through iManager to reset passwords
for users in their containers. I'm seeing through Console 1 that these
users also are granted Remote Control rights, based on their iManager
Role rights. I can live with that, but I need to block their ability to
change the properties of the package, such as blocking them from
unchecking the option that requires permission from the user before
allowing remote control. Any advice?
Thanks.

sherryhill,
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://support.novell.com/forums/

Manage Remote Desktop Settings

We have this set to "NO" in our client settings. However, I can right click on any client in the console and start the remote desktop client and connect successfully using RDP. So what exactly does the "Manage Remote Desktop Settings"
do?

>Where I am still confused is what the settings apply to.
> And what if RDP is already enabled by
me manually on a Windows machine? Than setting it to "yes" or "no" has no effect?
If "Manage Remote Desktop" settings is set to "No", then the client leaves the settings alone. Devices should continue on with whatever they have set locally.
If "Manage Remote Desktop" settings is set to "Yes", then the client will change the settings on devices to enable RDP and, optionally, add permitted viewers to the local "Remote Desktop Users" group or require network level authentication. according
to what you specify.
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer.

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...

Mountain Lion Server: add network user to remote management

Hi,
So recently I have upgraded from Lion Server to ML Server. A little disappointing, but whatever, I've moved on and got everything almost back to where I had it with Lion.
My last few issues I believe are related but can't quite figure it out. In Lion I have an admin profile and then a network user profile that I used on my MBP bound with AD. I'm at the stage where my nre network user can log in on the server machine but I can't log in as the network user via screen sharing. I can't add a network user to Remote Management, and with Remote Management enabled Screen Sharing is greyed out. I'd really like this to work.
My second problem is that I can't bind my MBP to the server but even when bound the network user account can't log in.
Any body have any ideas?
Thanks!

I had this problem on a clean install.
The solution was incredibly simple for me, but only after I saw Ross.M's note about opening the Users & Groups settings panel (in the OS System Prefs, not in server) and rebinding to OD server under Login Options.
That was not the solution for me, but under Login Options I discovered a previously unnoticed pref for "Allow network users to login at login window." I had this option set (apparently by default) to "Only these network users:" but with an empty list. Adding my users to the list made it work perfectly.
Talk about KISS

System Image Utility - Create User - Activate Remote Management

When creating an image with system image utility, based on a DVD image instead of a cloned image, I cannot create a user and activate Remote Management.
I have created an installer package with Apple Remote Desktop that is supposed to do both, however it doesn't work. I do not get an error, but no user is created.
I have tried a post-install script however the dscl command is not recognized even if I put the path /usr/bin/dscl.
I even tried to use a popular package out there called "createUser" but that fails as well.
Has anyone had any luck with this when trying to make a moduler image with System Image Utility?
Message was edited by: NeedSomeAnswer

After configuring all the appropriate settings, I
push the "Create" button and it appears to start
working, prompts me for a location to save the actual
image itself, creates a folder with the default name
and then nothing happens.
ok here's the deal: i created a folder in my OSX server home directory labelled "images" and keep our multiple images there. although you CAN have your images on other drives or on the network, that would take a LOOOOOOOONG time to do the data transfer to the invisible netboot folder on your server. my advice: keep local copies of all images. save a ton of time for yourself, eh?
then, when it's time to use the system image suntility to load up an image, i go to that same location each time, call it up and have the app set to the prefs i want or need. i'm on 10.4.7 server and have had no problem using the software.
so try using images locally and then, if that doesn't work, upgrade to 10.4.7

Remote Management service does not start

Has Novell got a fix for the issue where the Remote Management services
fails to start automatically on XP workstations? As we upgrade our clients
to XP, this has become a major headache. The service can be started
manually, and then the Remote Control feature of ZFD will work, providing
the firewall is disabled.

Workaround is to create a batch file and put in the command:
net start "remote management"
Create a shortcut to this batch file and put it in the startup group of
All Users in the "document and settings".
Phong Nguyen
> Novell Client 4.91 will not include any of ZFD 3.x services so you'll
need
> to upgrade to 4 or preferrably ZDM 6.5. This weekend I kicked off a
ZFD 3.2
> SP3 to 6.5 SP1 migration. Even without the extra services its worth it
just
> from a support stand point.
>
> Do the details posted in this thread help any?...
>
> Newsgroups: novell.support.zenworks.desktops.3x.remote-control
> Subject: ZfD3.2, NetWare 6.0, XPsp2, will it work?
> Message-ID: <azXhd.717$[email protected]>
> Date: Wed, 03 Nov 2004 02:41:10 GMT
>
> 1. Set Windows Firewall/ICS service to manual
> 2. Set Windows Firewall/ICS service to start before Remote Management
(ie.
> Remote Management service depends on Firewall/ICS and Workstation
Manager
> services)
> 3. Configure Windows Firewall exceptions for wuser32.exe, open ports
1761 -
> 1763 (you need others depends on the services you use, see TID below)
>
> What Ports are used by ZENworks Remote Management Agent?
> http://support.novell.com/cgi-bin/se...?/10054960.htm
>
> Support for Windows XP SP2 on ZENworks for Desktops
> http://support.novell.com/cgi-bin/se...?/10092958.htm
>
> --
> Tony Pedretti
>
>

Remote Management doesn't assign IP address, it displays (NULL)

Hi,
I hope some gurus can shed some light into this issue I'm having with Remote Management.
I have managed to remote access into my MB Pro once (using port forwarding) but after I put it into sleep mode I haven't been able to gain access since. When I go to System Preferences > Sharing > Remote Management my mac (or router) doesn't assign an IP address. It displays is the following:
Other users can manage your computer using the address (null).
Where the text says (null) I expected to see an IP address and I'm 99% sure the one time that Remote Access was working an IP address was assigned.
I can still access the Internet successfully, and I am running Snow Leopard (10.6.8). I've searched around the web and am at a dead end with a resolution. I've checked and rechecked my MBP's settings, I've also rebooted the wireless router but can't gain access.
What have I missed, or what am I doing wrong? Any help would be greatly appreciated.
Jeff.

I'm also interested to find out how you fixed this
regards

Remote Management and Windows VNC clients

Hey guys,
I recently had a go at getting the built-in VNC server in Leopard (as part of remote management) up and running.
Remote control works flawlessly from other Macs, but it refuses connections to Windows clients most of the time (throws up errors like 'Error waiting for server message' or something).
Any ideas? I thought it might have something to do with the Windows client not understanding the encryption, but haven't found any way to change security settings.
Thanks in advance!

Have you giving the server a VNC password?
System Preferences -> Sharing -> Remote Management -> Computer Settings -> VNC viewers may control screen with password: xxxxxxx
What VNC client are you using on Windows. Not all VNC clients are created equal? I know about TightVNC (which has been reported to work), RealVNC, and UltraVNC are 3 that I've heard about.
You can also install your own VNC server (in parallel using a different port or instead of the Mac OS X VNC). Vine Server (aka OSXvnc) has been used successfully for years. After all not all VNC servers are created equal either

Sharing - Remote Management - Allow Access = Broken

After upgrading to Mountain Lion, I was unable to connect to my new Mountain Lion remote desktops.
The upshot is that the Sharing -> Remote Management -> Allow Access settings are not AD/LDAP aware and it only works with local users now.
I had to turn off Remote Management and use Screen Sharing, where Allow Access is fully aware of local and non-local accounts.
Remote Managment -> Allow Access:
Screen Sharing -> Allow Access:
Your other option is to "Allow All Users" but I didn't want to do that.

I use the Vine Server for reduced color support. In my case it is my Mom's iMac 300 miles away and she has a slow DSL connection.
My experience with Mac OS X VNC server and client are that they work together very well, however, they do not play as nice with 3rd party clients and servers.
Since you are using Windows and by definition a 3rd party client RealVNC, I would suggest you install Vine Server. You can even configure it so it listens on port 5901 so it does not conflict with the Mac OS X VNC server.
<http://www.macupdate.com/info.php/id/11283/vine-server-%26-viewer>

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.

Remote Management settings

Similar Messages

Maybe you are looking for