ElliottRScott Absent Member.
Absent Member.
2027 views

Windows 2008 R2 proxy can't deploy to Windows 7 workstations

I'm trying to use a Windows 2008 R2 server as a proxy deployment agent. I have assigned a handful of Windows 7 workstations to the proxy to deploy agents. The workstations comply with the agent requirements, i.e. Simple file sharing turned off, Windows file & print sharing turned on, firewall rules to allow access, etc. When the Windows proxy tries to deploy the agents, the deployment tasks fails, and the messages on the proxy are the same for all workstations: (failed) Error: Can't contact target. I can't find any documentation that narrows down the reasoning behind this, and I don't know which log files would provide any further insight. I've reviewed the zmd-messages.log file and found a lot of data there (debug mode turned on), through which I can tell you the following information:

Things I can do:

1. I can access remote Windows 7 machines @ \\<hostname>\admin$ from the Windows proxy.
2. I can see proper resolution of dns names and IP addresses.
3. I can see in the zmd-messages.log file proper connectivity to the zenworks primary server.
4. I can verify that the certificate is identifiable by the WIndows proxy via the zmd-messages.log file.
5. I have verified the credentials being used and have test them via #1.
6. I can confirm successful registration with zenworks primary server.

I'll follow up with more, so this thread doesn't time out.

Elliott
Labels (2)
0 Likes
10 Replies
ElliottRScott Absent Member.
Absent Member.

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstat

Additionally: I had some issues after the agent was deployed on this Windows 2008 server. The server began the shutdown process, but behaved strangely. The zenworks server (OES11 SP1/SLES 11 SP2) crashed around the time I would have expected the Windows proxy to start communicating with it to register after the first boot-up after the installation.
0 Likes
Highlighted
ElliottRScott Absent Member.
Absent Member.

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstat

ZENworks 11.2.2 with December PRU installed and baselined.
0 Likes
ElliottRScott Absent Member.
Absent Member.

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstat

Clearing the zmd-messages.log and restarting the task, I see an irrecoverable error in the zenuserdaemon: [DeviceGuid] [] [Irrecoverable error!!! Error in creating Device session.] There are two of these events, I'm not sure if they are related.
0 Likes
ElliottRScott Absent Member.
Absent Member.

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstat

Also struggling to deploy Knowledge Base Files [3.6.A.2.16] on the same server. Not sure if this is related to the previous post.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstations

For Troubleshooting, Try using "PSEXEC" to remotely start any process on
the target box from the server using the same credentials supplied to ZCM.

This uses the same underlying technology.
Until that works, something is amiss in the setup.

Of course, Deployment Tasks to deploy the agent is something I always
consider a means of last resort when all other options are not available
due to the large number of configuration changes required to even allow
the feature to work.

Novell or MS Login Scripts.
ZDM7 or AG GPOs etc...
are all simpler.

At least in my mind, the ZCC tool is better at finding straggling
devices that trying do mass deployments.

On 12/26/2012 7:46 PM, ElliottRScott wrote:
>
> Also struggling to deploy Knowledge Base Files [3.6.A.2.16] on the same
> server. Not sure if this is related to the previous post.
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
ElliottRScott Absent Member.
Absent Member.

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstat

Interesting commentary. Thanks, Craig.
0 Likes
ElliottRScott Absent Member.
Absent Member.

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstat

Funny, I've had success with this during my initial testing. I deployed to a WinXP box and a Win 7 box w/out problems.

The psexec worked with the credentials I'm using for zen... It would help if I could better understand what the error, "Can't contact target", meant. This has to be feedback from some instruction being executed. Any insight?
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstations

I think it means just what it says.
Perhaps the Device's IP changed between scan and deployment.
Perhaps the Device was off or even too asleep to accept the remote
install task.



On 12/27/2012 11:26 AM, ElliottRScott wrote:
>
> Funny, I've had success with this during my initial testing. I deployed
> to a WinXP box and a Win 7 box w/out problems.
>
> The psexec worked with the credentials I'm using for zen... It would
> help if I could better understand what the error, "Can't contact
> target", meant. This has to be feedback from some instruction being
> executed. Any insight?
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
ElliottRScott Absent Member.
Absent Member.

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstat

Hi Craig,

Unfortunately, it's not due to some of the suggestions you've left here. The machine is awake. I can access it via psexec, immediately before and after the test. No configuration changes have taken place. I suspicious that the error is pointing back to the ZENworks server. Is there a log file where I can research this more intensely?

Elliott
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Windows 2008 R2 proxy can't deploy to Windows 7 workstations

This may help with logs to isolate the issue........(Yes, if PSEXEC is
working, definitely looks like a ZEN issue. Any chance the IP changed
between discovery and deployment? Just a guess, i dont know that would
even cause an issue.....)

http://www.novell.com/support/kb/doc.php?id=3418069

Component Name: Deployment
Enable Debugging (self documenting xml file. Set to FINEST):
Windows server:
%ZENWORKS_HOME%\conf\loader\deployment.xml
Linux server:
/etc/opt/novell/zenworks/loader/deployment.xml
Restart loader service. (novell-zenworks-configure -c Start) will give
you the option to restart.

Note: Modify the existing xml file. A file called "copy of
discovery.xml" in the same directory will be used if it exists.


Log Location:
Windows server:
%ZENWORKS_HOME%\logs\loader-messages.log
Linux server:
/var/opt/Novell/log/zenworks/loader-messages.log
Windows Workstation:
ZDPASERV.EXE service logfile c:\RemoteSvc.log
%temp%\wincustomaction.log
event log viewer for preagent events

For linux servers that use Windows discovery/deployment proxy,
additional logging will be in zmd-messages.log on the proxy device (set
to debug).



On 1/7/2013 2:56 PM, ElliottRScott wrote:
>
> Hi Craig,
>
> Unfortunately, it's not due to some of the suggestions you've left
> here. The machine is awake. I can access it via psexec, immediately
> before and after the test. No configuration changes have taken place.
> I suspicious that the error is pointing back to the ZENworks server. Is
> there a log file where I can research this more intensely?
>
> Elliott
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.