New Boundary Support Forum
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      



Client installation failureExpand / Collapse
Author
Message
Posted 7/28/2005 1:09:00 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 7/28/2005 12:35:00 PM
Posts: 1, Visits: 1

Hello folks,

When I attempt to push the Prism client using the Direct Method, I get an error Access Denied.  After investigating I see in the Computer Status Reports the computer I attempted to install has a note in the "Client Install" column.  Note is "Direct Install Failed (registry access).

I have been able to use the same console and channel to install to other machines, and push packages to those other machines.

 

Post #1001
Posted 7/29/2005 2:05:00 PM


Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: Today @ 9:14:58 AM
Posts: 658, Visits: 838

It sounds as if this particular machine is more locked down than the others. In order for direct push to work, the Remote Registry service must be enabled. One way to test if you have remote registry access is to launch regedit on the Prism server, then choose File|Connect Network Registry. Type in the name of the computer you're trying to install. Can you browse its registry through regedit, or do you still get access denied?

Other ideas: Is the target system running a firewall?  Is the user on the target system a local administrator? If so, it's possible the user made some access changes that would prevent you from being able to remotely manage it.

Sometimes a problem with permissions on a certain registry key can cause this behavior. Here are some things to try. Obviously, in order to do this you'll have to either be able to remotely connect to the system or else be physically at the computer: 

  1. Run regedit and navigate to the following key: HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
  2. Right-click on winreg and click Permissions.  If LOCAL SERVICE is present, make sure the account has read permissions. If LOCAL SERVICE is not present, locate and add the account, giving it read permissions.
  3. Next, expand the winreg key so that AllowedPaths subkey is selected, and double-click on the Machine data item on the right. Initially, all data will be highlighted. Click just below the highlighted area and add the System\CurrentControlSet\Control\Windows if it doesn’t already exist.  Note: if you accidentally clear the window of all data, click "Cancel", and try again.

After making these changes, try direct installation again.





New Boundary Technologies Support
support@newboundary.com

Post #1003
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: New Boundary Support

PermissionsExpand / Collapse

All times are GMT -6:00, Time now is 1:06pm

Powered By InstantForum.NET v4.1.3 © 2008
Execution: 0.172. 14 queries. Compression Enabled.