Remote Management Freezes computers

When ever I remote manage a user who is running an application in the Oracle instant client it freezes there Internet Explorer. I have to force the program to end now and then the user can go back into the oracle app and everything works fine.
Any Ideas??? Kind of a big problem being that most users call with a problem in Oracle and we cant see the problem since we freeze everything when we remote manage.

jortman83 wrote:
>
> I am running ZEN7 sp1 hp6 on a Netware 6.5 sp6 server. The
> workstations that freeze up are Windows XP pro sp2. You remote into
> their workstation and can view the oracle application they are in
> which runs in IE 6. But as soon as you click on any field IE6 locks
> up and turns all white and then you have to use task manger to close
> IE6. If they are not in the Oracle app you can remote manage them
> with out a problem
what would happen if IE was upgraded to 7??? still the same problem?

Similar Messages

Remote Manage computers that are not on my LAN.

Hi.
i want to be able to remote manage laptops & desktops that are not on my LAN all running 10.6.4
i want to be able to ARD and get logs and even changed settings in workgroup manager if i can.
ideas?
would wide afea bonjour achieve this for me? or is there better options ideas out there.
just a note: i would still like to use apple remote desktop. not some web client like log me in.
and also just a random question, if i have laptops that are bound to the directory but the users home folder is on the device. if they were to change there password on the LDAP / login, mail, CalDAV password. would that update the laptop not on our LAN. so the user has to login with there new password?
you might be asking why: new start up company with a lot people spread across to countries. and i wont to enforce password has to change every 28 days for their login, mail, CalDAV, CardDAV etc.
Message was edited by: -{ jonohayes }-

i want to be able to remote manage laptops & desktops that are not on my LAN all running 10.6.4
I'm not sure I understand the question. ARD isn't limited to machines on your LAN. You can manage any machine you have TCP/IP connectivity to - in other words, if you can ping the machine you can (probably) manage it via ARD.
The only issue you may have is that the Bonjour auto-discovery mode won't necessarily find remote machines - you obviously don't want it scanning the entire internet for available machines, so you can either use the Scanner and define a range of IP addresses to check, or specify the remote machine's IP address directly.
and also just a random question, if i have laptops that are bound to the directory but the users home folder is on the device. if they were to change there password on the LDAP / login, mail, CalDAV password. would that update the laptop not on our LAN. so the user has to login with there new password?
Impossible to answer with the data provided.
If the user's account is on the Open Directory server, then changing the password on the LDAP server will require them to login to their laptop with their new password.
However, it's also entirely possible that the users have local accounts on their machines and just use Open Directory for server-side functions (mail, etc.). In this mode account 'joe' in Open Directory might not be the same account 'joe' on the Open Directory server. As such, changing the Open Directory server will require the user to use the new password for the server-side functions, even though they continue to log on to the laptop with their old account/password.
Only by looking at the machine's configuration will you know which mode you in (or trying it and seeing what happens, I suppose )
i wont to enforce password has to change every 28 days for their login, mail, CalDAV, CardDAV etc.
Personally, I hate this approach. Forcing users to change passwords frequently results in users choosing weak passwords because they don't have time to learn the muscle memory that eases the typing of complex passwords. Moreover what you'll often find is that users choose the same password stub and just append a number on the end - kind of like 'password1' -> 'password2' -> 'password3', etc., which is barely useful.
It's your company, though, and this is just my personal opinion. A better solution hinges on having an effective notification and account revocation process (i.e. if someone's account gets compromised it can be shut down quickly).

Remote Managing remote computers

I don't know if this is a question for the Remote Management area since it's also probably a mid-tier question.
I should first mention that we currently are using ZEN 7 looking possibly to upgrade to ZEN 10 next year, but looking at possibly adding a mid-tier server this year.
We are trying to find a solution to remote manage machines outside of the corporate network. We have about 30 machines at about 20 remote sites that sit outside of our corporate network. These machines don't have a hardware VPN tunnel, but rather a software VPN connection to access network resources. Some of these machines are used on a regular basis and some of them might go untouched for 30-60-90 days or even more.
Anyway, since these machines all do have software VPN on them, we want to stay on top of the machines as far as policies, antivirus updates, windows updates, and everything else. Without being able to remote manage them, it becomes difficult.
My question is whether it is possible, using a mid-tier server, can we administer these machines remotely without a user being there to sign in to the software VPN and give me ip information? A lot of these machines are always on, but not always connected to the network w/ the software VPN which times out after x-amount of time (a day, a week... I'm not sure). A lot of the documentation I've been reading seems to indicate that users use the desktop management agent to login thru the mid-tier server which sits in a DMZ which authenticates to the ZENworks server. I guess I want to know if we can get at these machines if we have a static IP and the machine is on, but it isn't logged using the Desktop Management Agent or Novell Client.
Thanks,
Brent

Sorry about bumping my own post, but does anyone have any ideas?
Thanks,
Brent

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

Manage multiple computers from out side

Hi ,
i want to manage 2 computers from out side my network. Ihave time machine, dynamic ip, wha ti wanted is able to log in from out side to this 2 computers. what is the best option ?
thanks in advnace

power mac, you could use other software like timbuktu or logmein. If you wanted to you Apple Remote Desktop, you would have to set up VPN so the mac you would be using to control the other ones is part of the network.
Regards.

In System Preferences- Sharing- Remote Management the address doesn't reflect the computer name.

Hi,
I have a dual boot system with two seperate hard drives, Lion and Snow Leopard. One drive has a name of mac-pro2 for Lion and mac-pro2sl for Snow Leopard. Something happened when I rebooted from Snow Leopard to Lion that in System Preferences->Sharing->Remote Management that the computer name had changed to the Snow Leopard computer name it has a address and name of mac-pro2sl. I have change the Computer Name: and it worked and was changed to mac-pro2 but Remote Management still has the address of mac-pro2sl and doesn't reflect the computer name. I can ssh into Lion with mac-pro2sl but I have a conflict with from other computers when I log in with a warning of "Remote Host Identification has Changed". How do you change the computer name for remote management and ssh?
I have changed the hostname and it reflects the change when you login, mac-pro2 for Lion. But when you ssh into Lion it requires mac-pro2sl not mac-pro2.
When I change the computer name it shows below that the name in "Remote Management: On" "computer using the address mac-pro2sl" is selected but then doesn't change but remains the same when the dialog closes. How do you change the address to reflect the computer name? Is there a command line utility?
Thanks for any help.

If this problem is due to DNS, look in your configuration. What is the number one DNS server address? Is it local, or is it on the Internet at large? Or post the Address here and folks can help you look it up.
192.168.yyy.zzz
10.xxx.yyy.zzz
172.xxx.yyy.zzz
are all strictly local.

Back to My Mac / Remote Management / Screen Sharing

I'm managing computers for my family spread across 3 states. I would love to get screen sharing working but it's just not happening. I've tried the steps in the following KB article and that's allowed me to access two mini servers (one 10.7 and one 10.6.8) at home. However, I can't access a MBP at home and I can't access my family's computers (via screen sharing) at all. Here's the KB article...
http://support.apple.com/kb/HT3486
Here's all I'm seeing (5 computers are "missing")
I've tried NAT port forwarding (Airport Extreme/Time Capsule) for "Apple Remote Desktop" to the computers internal IPs on ports 5900 & 3283. I've tried it without. I've tried both "Screen Sharing" and "Remote Management" in preferences. I've made sure I have my own account with admin privledges on all machines etc. This is, of course, all peppered with the occasionaly outburst of foul language...
What am I missing?

Spoke with Apple who spoke with Apple and so on. Tech support for Apple Desktop Remote acknowledges (as best they could) that there is a bug/ problem. Yes, reverting to an older (3.5 - 3.4 ARDagent) solves the problem (short term ?). They captured my OS info and will get back to me in 3-5 days - how do you like them apples! So, revert to ARDagent 3.4 and you can remote connect - may try this later... will post if it works. Here's what's been posted on this: https://discussions.apple.com/thread/3192451?start=0&tstart=0

DNS, WINS, CompMgmt.msc Remote Management 2003 -- 2008-R2

My client has 3 WINS Servers which are (generally) replicating (push/pull partners all around).
In the MMC for WINS (and other services/consoles, CompMgmt and DNS specifically) we can add and connect from the 2008-R2 to the 2003 WINS (etc.) Servers.
From the 2003 to the 2008-R2 the connection fails with "Access denied".
The AD Users and Computers has no such issue.
I initially presumed that it must be either a port filter or some (perhaps obscure) registry/GPO security setting.
FYI: All of this is through an RDP session.
Any ideas on how to check and troubleshoot this?
HerbM

We have the local firewall turned off and all indications are that the switch/router firewalls are not blocking any of this. (These are all within one organization and and the checks that I have made have shown everything to be open.)
What specifically would need to be open for such remote management? Feel free to send me to some web resource etc. but so far I haven't found anything that would give me a definitive checklist.
I am pretty good with firewalls and such, good enough to be fairly certain that this is an open network, but also good enough to know that SOMETHING could be filtered that I am unaware of.
And it does actually say, "Access" denied.
-- HerbM

Remote Desktop: See computers but will authentication fails

I have installed Remote Desktop. See the other computers on the network. Authentication fails

on the computers (Macs) you're trying to control...
under Apple menu > System Preferences > Sharing
do you have "Remote Management" enabled? and have an account selected under "Allow access for"?

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.

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.

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

Remote Management Config on NetInstall

Hello.
Is it possible to configure the Remote Management of a system when creating the Netinstall image? Say for example I install 100+ systems, I don't want to hook each one of these into a screen and manually configure Remote Management.
Any advice or pointers on things to read up on would be great.
Thanks.

Hello.
Is it possible to configure the Remote Management of a system when creating the Netinstall image? Say for example I install 100+ systems, I don't want to hook each one of these into a screen and manually configure Remote Management.
Any advice or pointers on things to read up on would be great.
Thanks.

Remote Management Freezes computers

Similar Messages

Maybe you are looking for