Remote Management lists server IP

Hello,
I have a NW6 server running Zen 4.0.1 and when I right-click on a user
object and click "Remote Management" it lists there IP and the IP of the zen
server. This only happens on some machines, most work fine.
We are a mixed IP/IPX environment.
Any ideas or reasons this may happen???
Scott Windmiller
University of Maryland
Department of Psychiatry
Information Systems

On Tue, 02 Nov 2004 14:59:52 GMT, Scott Windmiller wrote:
> I have a NW6 server running Zen 4.0.1 and when I right-click on a user
> object and click "Remote Management" it lists there IP and the IP of the zen
> server. This only happens on some machines, most work fine
hmm the zenserver ip could show up because the user is using the
middletier..
Marcus Breiden
Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

Similar Messages

Remote management via Server app authentication issues

I am having issues with server app. I can login to my home server if I choose the "other computer" option and input the IP address of the server and respective authentication information, but if I acutally choose server that appears in the "manage" screen, server.xxxxxx.private, the authentication fails. Go figure. I also had this issue when I when to bind our other computers to the server.
What could cause this issue?

I figured it out! I had to add the IP of the server as a DNS Server in Network preferences Advanced Tab. Also binding worked as well when I did this.

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

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 in Remote Web Access - "An unexpected error occurred. Please try again. If the problem continues, contact the person who manages your server."

I have set up the RWA and I can log in to the web console with my server account. However when I click on any of the shared folders I get this error:
An unexpected error occurred. Please try again. If the problem continues, contact the person who manages your server.
Does anyone know how to troubleshoot this?
Regards,
Maciek

I had this very same issue with one of our customer's servers that was running Windows Server Essentials. I ended up calling Microsoft about the issue. I hope this helps someone. This originally appeared on my blog: http://techspeeder.com/2014/01/14/remote-web-access-error-an-unexpected-error-occurred/
Troubleshooting Steps:
1. We were getting unexpected errors while accessing shared folders remotely
2. The tech found IIS handlers were missing
3. She went to IIS > server level ( parent level) and added managed handler mapping :
Name: svc-Integrated-4.0
Request path: *.svc
Executable: System.ServiceModel.Activation.ServiceHttpHandlerFactory, System.ServiceModel.Activation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
4. Added script mapping:
Name: svc-ISAPI-4.0_64bit
Request path: *.svc
Executable: windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
Name: svc-ISAPI-4.0_32bit
Request path: *.svc
Executable: windir%\Microsoft.NET\Framework32\v4.0.30319\aspnet_isapi.dll
5. Ran IISreset.
6. We were able to access resources in Remote access, then.

Server 2012 R2 - Remote Management Exception - Not working 100%

So,
I am spinning up a ton of VM's for the University I work at in preparation for migrating to 2012 completely and I discovered something interesting today.
The "Allow Remote Management from these subnets" option, only partially enables remote management. You still need to run the remote management enablement with NetSh (http://blogs.technet.com/b/askds/archive/2008/06/05/how-to-enable-remote-administration-of-server-core-via-mmc-using-netsh.aspx)
for the certain functionality (Remote Firewall, VDS, FRS Options), which to me seems really weird.
Has anyone else experienced this?
----------------------------------------- Dan Sheppard

Hi Dan,
If you want to manage remote server core with MMC (Microsoft Management Console), we need to configure Windows Firewall firstly to allow MMC snap-in(s) to connect on the remote server core, since your servers are Server 2012 and newer, so we can also use
the powershell cmdlet instead of cmd netsh:
Enable-NetFirewallRule -DisplayGroup "Remote Service Management"
In addition, you can also use Windows Powershell to help you to remote access with Powershell Remoting, Powershell has substantial Modules and Cmdlets to help us to manage server.
For more detailed information to manage server core, please refer to this article:
Manage a Server Core Server
If there is anything else regarding this issue, please feel free to post back.
If you have any feedback on our support, please click here.
Best Regards,
Anna Wang
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Odd firewall issue, remote management works on 1 server, not the other

I've enabled port forwarding, made sure I mapped address to mac ports in the DHCP client settings (to ensure a "static" address), and choose the correct IP address for port forwarding. Then, I enable remote management on my snow leopard laptop then connect remotely (from outside lan) and it works. To the reverse, my 10.5.8 OS X server set up with the same items (although the menus are slightly different given each are diff versions), change port forwarding IP addresses on router, and try outside the lan from the client to connect to the server. Failed. Of course, remote management works fine on the LAN in both directions, only fails from snow leopard client to 10.5.8 server when not on same lan.
So, to illustrate:
10.5.8 (client) ---> internet --> router --> snow leopard laptop (server) WORKS!!
snow leopard laptop (client) --> internet --> router --> 10.5.8 (server) FAILS!!!
client --> LAN --> server (in either direction) WORKS!!
Message was edited by: julebuggy

I've enabled port forwarding, made sure I mapped address to mac ports in the DHCP client settings (to ensure a "static" address), and choose the correct IP address for port forwarding. Then, I enable remote management on my snow leopard laptop then connect remotely (from outside lan) and it works. To the reverse, my 10.5.8 OS X server set up with the same items (although the menus are slightly different given each are diff versions), change port forwarding IP addresses on router, and try outside the lan from the client to connect to the server. Failed. Of course, remote management works fine on the LAN in both directions, only fails from snow leopard client to 10.5.8 server when not on same lan.
So, to illustrate:
10.5.8 (client) ---> internet --> router --> snow leopard laptop (server) WORKS!!
snow leopard laptop (client) --> internet --> router --> 10.5.8 (server) FAILS!!!
client --> LAN --> server (in either direction) WORKS!!
Message was edited by: julebuggy

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.

ADF Library Error on Remote Managed Server for Clustering

I wanted to configure 2 managed servers on different PCs for clustering. For this purpose first I created 2 managed servers on my test domain which is on my PC1. Tested my ADF applications for each managed server (srv1 and srv2) on PC1. They passed. When I moved one of these servers to another PC (PC2) with the following commands below, the commands said it was succeeded.
on PC1:
pack -managed=true -domain=E:\Oracle\Middleware\user_projects\domains\test_domain -template=E:\Oracle\Middleware\user_template\TEST_DOMAIN.jar -template_name="TEST"
onPC2: (Remote PC)
unpack -domain=test_domain -template=D:\oracle\Middleware\user_template\TEST_DOMAIN.jar
After these steps, I started my servers on command line by using the commands below:
on PC1:
startManagedWebLogic.cmd srv1 http://localhost:7011
on PC2: (Remote Managed Server)
startManagedWebLogic.cmd srv2 http://30.1.2.192:7011
srv1 changed its state to RUNNING mode easily, however srv2 changed its state to RUNNING with a lot of errors which were pointing that the ADF libraries and applications couldn't be found.
After the errors on srv2, I removed srv2 from the targets of libraries by using the Deployments screen of administration console.
Then I stopped srv2 and started it by using command line. It worked without any library and application. There was no error.
After those steps, I want to add srv2 to the targets of libraries. When I tried to do this I faced with the error message below:
An error occurred during activation of changes, please see the log for details.
[Deployer:149003]Unable to access application source information in 'E:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adf.oracle.domain.ear' for application 'adf.oracle.domain [LibSpecVersion=1.0,LibImplVersion=11.1.1.2.0]'. The specific error is: [Deployer:149158]No application files exist at 'E:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adf.oracle.domain.ear'..
My applications can not run without ADF libraries and I couldn't find any solution to the error above.
Can anyone help me on this subject

Hi,
<h3>Please Confirm Point -1 :</h3>
NOTE: the Absolute Path of the *"WLS Installation"* and *"Domain Directory"* must be same (Identical) in both the BOXES. Looks like the Path *"E:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adf.oracle.domain.ear"* doesnt exist in your Remote Box (PC-2). D:\oracle\Middleware.
I Think mistakenly u have installed WLS in <font color=red>E:\</font> in one Box and <font color=red>D:\</font> in another Box.
<h3>Please Confirm Point -2 :</h3>
Please refer to the following link: http://download.oracle.com/docs/cd/E12839_01/webcenter.1111/e12405/wcadm_deploy.htm#BABEJEEA
Which says that you must install a few Libraries (including ADF) in order to utilize the ADF features ...in every Managed Server, to avoid these kind of issues. You must deploy the following libraries to the new managed server or cluster:
<font color=maroon><b>
adf.oracle.domain(1.0,11.1.1.0.0)
adf.oracle.domain.webapp(1.0,11.1.1.1.0)</b></font><BR>
jsf(1.2,1.2.9.0)
jstl(1.2,1.2.0.1)
ohw-rcf(5,5.0)
ohw-uix(5,5.0)
UIX(11,11.1.1.1.0)
<font color=maroon><b>oracle.adf.dconfigbeans(1.0,11.1.1.0.0)
oracle.adf.management(1.0,11.1.1.1.0)</b></font><BR>
oracle.dconfig-infra
oracle.jrf.system.filter
oracle.jsp.next(11.1.1,11.1.1)
oracle.sdp.client(11.1.1,11.1.1)
oracle.soa.workflow.wc(11.1.1,11.1.1)
oracle.webcenter.framework(11.1.1,11.1.1)
oracle.webcenter.framework.view(11.1.1,11.1.1)
oracle.webcenter.jive.dependency(11.1.1,11.1.1)
oracle.webcenter.skin(11.1.1,11.1.1)
oracle.wsm.seedpolicies(11.1.1,11.1.1)
oracle.portlet-producer.jpdk(11.1.1,11.1.1)
oracle.portlet-producer.wsrp(11.1.1,11.1.1)
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

Connector Server Vs Remote Manager

If your connector requires/supports connector server, is remote manager needed at all anymore for that connector?

To those of you here in this thread, I have a question about Vine and autostart in OS 10.5.
I configured autostart (through the Users Systems Preference) to include Vine. When the mac starts, it puts the round green Vine icon in the dock, but it does not actually start it. To do that, I must click it. That causes the icon for the volume (the white box) to appear on the desk top, a white dot to appear beside the green icon (saying its running), and a screen to appear that says the server is running, which, when minimized becomes a screen icon under the dock divider bar.
It would seem all I have to do is click "Open on Login" on the green icon in the dock. I do that. But it doesn't stick for the next re-start. Restart puts the green icon in the dock, but "open at login" is no longer checked (which is why it doesn't start).
In summary, what I have done causes the Vine icon to appear in the dock on a boot, but does not actually start it.
Any ideas how I proceed?

Vista, IE7 and Virtual Office (VO) or Remote Manager

A Windows Vista laptop (Vista Business Edition) is trying to browse to the Virtual Office web page published by their Novell SBS 6.5 server using IE7. Nothing appears in the browser. If I look at the source for the page, there is a bit of code showing, referencing a Java script. I get the same result when I try to use the Netware Remote Manager web page at http://servername:8008 or https://servername:8009. It is the same if I use the server's IP address instead of a resolvable name. The browser windows says "Connecting" and the status line shows "Waiting for 10.170.170.5"
I loaded up Firefox, and after allowing a Certificate Exception, I am able to browse to the server's Virtual Office page from the same computer.
I have installed the Certificate from the server into the Trusted Publishers container, I have set both the http://servername and https://servername into the trusted sites list.
What else do I need to do in Vista to get the web page to work?

The answer is to turn off TLS 1.0 in the Advanced Internet Options
page.
Warren
On Wed, 06 May 2009 01:56:01 GMT, WFRUSH
<[email protected]> wrote:
>
>A Windows Vista laptop (Vista Business Edition) is trying to browse to
>the Virtual Office web page published by their Novell SBS 6.5 server
>using IE7. Nothing appears in the browser. If I look at the source for
>the page, there is a bit of code showing, referencing a Java script. I
>get the same result when I try to use the Netware Remote Manager web
>page at http://servername:8008 or https://servername:8009. It is the
>same if I use the server's IP address instead of a resolvable name. The
>browser windows says "Connecting" and the status line shows "Waiting for
>10.170.170.5"
>
>I loaded up Firefox, and after allowing a Certificate Exception, I am
>able to browse to the server's Virtual Office page from the same
>computer.
>
>I have installed the Certificate from the server into the Trusted
>Publishers container, I have set both the http://servername and
>https://servername into the trusted sites list.
>
>What else do I need to do in Vista to get the web page to work?

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.

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

Disk Management Remote Management

Playing with remote management of disks using Disk Management on Windows Server 2012 R2. Looks like Microsoft is making progress, as it appears I am able to handle most functions now. But I've seen some anamolies in regards to seeing the results
of the actions I take.
I find that before I can see the results of the action I take, I need to first change Disk Management to look at a different computer and then come back to the one I was working on. For example. I am on Server1 but looking at Server2. I
perform the simple act of placing a disk on Server2 online or offline., but I cannot see the completion. However, if I simply connect Disk Management back to Server1 and then reconnect to Server2, I see the result. If I format a disk, I need
to refresh the display to show the results, so it seems to be partially working. (If formatting locally, I don't have to refresh.)
Again, this is more than I was able to get done with 2008, so I like the improvements. But, it seems like there still needs to be a little more work done on it.
.:|:.:|:. tim

Johan/Vincent,
Thanks for pointing me to Server Manager. I guess I am so used to using Disk Management that I totally ignored the new interface. Yes, it works much better - that's not to say that the problems I reported above should not be resolved, unless
it is Microsoft's intention to do away with Disk Management in the near future and move everything to Server Manager.
I did find some strange things with Server Manager, though. First was that when I selected the new disk and requested to bring it online it reported that it was already online to another server - which I know to be absolutely false.
Secondly, when I selected the disk and requested to initialize it, even though it was only a 10 GB disk, it forced it to be a GPT disk - didn't even give me the option of an MBR. Not a problem in my case, as I tend to make everything GPT.
Lastly, when I started the New Volume wizard, it took a long time to enumerate the environment. In Server Manager, I had five hosts and a total of 17 disks. And it took that long, even though I had right-clicked on the disk I wanted to format.
Seems a little odd to enumerate everything when I had already selected which disk to format.
Again, thanks for the heads-up on Server Manager. I am going to try to remember to try it first now instead of falling into my old habits. But please pass on these additional things I have run into.
EDIT: I think I found the cause for the long time to enumerate. I don't know how it happened, but I had a bogus remote server being 'managed'. The name looked like a default name from a new build. I may have been playing around trying
to access a non-domain joined server. The interesting thing is that it was not showing up in the list of servers. I found a reference to it in an error message. It was saying it was part of a cluster, which was really, really strange and
I have no idea how it came to that conclusion. So I released the cluster from Server Manager, re-added it, and now enumeration works fine. Very strange.
.:|:.:|:. tim

Remote Management lists server IP

Similar Messages

Maybe you are looking for