Zenworks Agent 10.3.3 - Windows 7 32 -Strange behavior

Hi,
Here's my problem :
I have a SYSPREP fully functionnal that install the Novell Client IR9a on a Windows 7 SP1 32Bits and at the end i have a VBS File that download the latest version of Zenworks Agent installer to the local harddrive. After it installs it... Then a strange behavior happen after the required reboot by the installer.
You can't ping any DNS names until until you have rebooted your machine 3 times.
-> You can ping ip addresses but not their names.
I tried to do a flush dns realse or renew and same behavior... can't ping any DNS names.
This problem is not there if i do not install the Adaptive agent and leave the Novell Client Alone...
The Windows 7 was originally a home premium that was upgraded to a oem pro license if that can ring any bell.
Thank you.

There was an issue a LONG time ago that I have not heard reported
since..........
http://www.novell.com/support/viewCo...rnalId=7004310
Maybe the old work-around will help you...........
On 1/16/2012 2:46 PM, anto28 wrote:
>
> Hi,
>
> Here's my problem :
>
> I have a SYSPREP fully functionnal that install the Novell Client IR9a
> on a Windows 7 SP1 32Bits and at the end i have a VBS File that download
> the latest version of Zenworks Agent installer to the local harddrive.
> After it installs it... Then a strange behavior happen after the
> required reboot by the installer.
>
> You can't ping any DNS names until until you have rebooted your machine
> 3 times.
>
> -> You can ping ip addresses but not their names.
>
> I tried to do a flush dns realse or renew and same behavior... can't
> ping any DNS names.
>
> This problem is not there if i do not install the Adaptive agent and
> leave the Novell Client Alone...
>
> The Windows 7 was originally a home premium that was upgraded to a oem
> pro license if that can ring any bell.
>
> Thank you.
>
>
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.

Similar Messages

DFS and Windows 7 x64 strange behavior when trying to access a DFS link through mapped drive

I've manually mapped a network drive (Q Drive) to a DFS location. Whenever I go into "My Computer" and open the Q Drive it shows the DFS links but when I double click one of the links it randomly takes me back to the "My Computer" starting point showing my standard drive letters. If I click through the Q drive and the DFS several time it all of the sudden works. Sometimes this circle of clicking can go on for 5-10 times before it works properly.
I'm running the x64 edition of Windows 7. Any suggestions on how to make this work properly? Its very annoying.

GPO mapped namespace where you can't connect through the mapped drive letter but can connect through the DFS UNC namespace? Do you use access based enumeration?
I personally think it has something to do with network bandwidth, the security token and offline files. =)
You can access the namespace itself but not any of the linked shares (try checking the ACL:s on the shares and you get permission denied, but you still see them, ie they are listed).
I found a post sometime ago about corrupted/trunkated security tokens. If the member was part of too many AD groups the token was trunkated and corrupted. That was going to be my next move. Sniff the traffic and see what actually happens when the issue occur
if theres something to be learnt there. Since it works correctly through the UNC adress but not through the drive letter you ough to be able to see what is different between the two requests.
http://blogs.technet.com/b/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx
One thing I noted was that it only happened to remotely connected computers on slow 3G connections (we use Direct Access). Never on LAN-connected computers with GB access or remote computers with fast (>15Mbps) access. We also use folder redirection,
which I think could be part of the problem, ie the share never goes online, atleast for us the issue was itermittent, it never happend all of the time, just from time to time. And if I disconnected and reconnected it could fix the issue for that particular
sessions, usually it didn't but occasionally it did (just pulling the network cable and put it back). Check the offline/online status the folders show up as offline even though they are online.
Enough of my ramblings. Sorry to hear you still have the problem and I hope you find a way to solve it.

Hosting Zenworks 7 Application Files On Windows Server?

Hi,
Background:
We currently host our Zenworks packages on Netware 6.5 servers. Our Zen7 is also installed on a Netware 6.5 server so we are running Novell Client 4.91 SP2 and the Zenworks agent on our Windows XP SP3 desktops (no middle tier).
We are now in the process of moving to Active Directory, and one of the first steps will be to migrate file services over to Windows shares. We currently use either the MSI feature of NAL to elevate rights or we use unsecured system user to elevate rights as our users are not Administrators of their workstations. We associate our application objects to either user container, user group, or simply invidual users. Our login scripts map drive letters to our Netware shares. Our MSI objects in NAL access the packages via the mapped drive letter while our normal objects (unsecured system user) access them by UNC path or by using application file distribution feature of NAL.
Questions:
Will there be any issues with moving the application files from Netware to Windows? What file permissions would we have to grant on the Windows side to allow the Zenworks agent to access the file shares? I know on the Netware side, we would grant read rights to the file share to the same containers, users, or groups that have access to the application object. We also granted our workstations container access to certain directories so that the unsecured system user could access the shares via UNC path. I've seen some discussion on the forums about using the built-in Everyone account on the Windows side. Would there be additional accesses required? What about the security implications of granting Everyone read access to these shares? I'm just trying to get an idea of what would be needed on the Windows side to allow Zenworks to keep working. Obviously we'll probably be keeping our eDirectory infrastructure at least until all phases of the migration are complete.
Thanks in advance!

You can Grant FileSystem Rights to DomainWorkstationObjects just as you
granted rights to ZENworks Workstation Objects.
These rights will be used by processes running in the SYSTEM space.
The result should be that there would be little issue with using a
Windows Share in lieu of a NetWare share for ZDM7.
On 4/29/2010 4:46 PM, joshbilsky wrote:
>
> Hi,
>
> BACKGROUND:
>
> We currently host our Zenworks packages on Netware 6.5 servers. Our
> Zen7 is also installed on a Netware 6.5 server so we are running Novell
> Client 4.91 SP2 and the Zenworks agent on our Windows XP SP3 desktops
> (no middle tier).
>
> We are now in the process of moving to Active Directory, and one of the
> first steps will be to migrate file services over to Windows shares. We
> currently use either the MSI feature of NAL to elevate rights or we use
> unsecured system user to elevate rights as our users are not
> Administrators of their workstations. We associate our application
> objects to either user container, user group, or simply invidual users.
> Our login scripts map drive letters to our Netware shares. Our MSI
> objects in NAL access the packages via the mapped drive letter while our
> normal objects (unsecured system user) access them by UNC path or by
> using application file distribution feature of NAL.
>
> QUESTIONS:
>
> Will there be any issues with moving the application files from Netware
> to Windows? What file permissions would we have to grant on the Windows
> side to allow the Zenworks agent to access the file shares? I know on
> the Netware side, we would grant read rights to the file share to the
> same containers, users, or groups that have access to the application
> object. We also granted our workstations container access to certain
> directories so that the unsecured system user could access the shares
> via UNC path. I've seen some discussion on the forums about using the
> built-in Everyone account on the Windows side. Would there be
> additional accesses required? What about the security implications of
> granting Everyone read access to these shares? I'm just trying to get
> an idea of what would be needed on the Windows side to allow Zenworks to
> keep working. Obviously we'll probably be keeping our eDirectory
> infrastructure at least until all phases of the migration are complete.
>
> Thanks in advance!
>
>
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.

Script uninstall of zenworks agent how ?

Hi!
Anyone knows how to uninstall zenworks agent with a script ?

The uninstall string should be in the registry along with the other programs
in add/remove programs.
hklm\software\microsoft\windows\currentversion\uni nstall
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 :> )
<[email protected]> wrote in message
news:eu6Ef.1563$[email protected]..
> Hi!
>
> Anyone knows how to uninstall zenworks agent with a script ?

ZenWorks Agent and Windows7 - No dynamic User

Hello we have Open Workgroup Suite 2.5 Small Business Edition. With the last automatic update.
Now we have new PC's with Windows7 SP1.
Problem: Windows 7 SP1 does not Register the PC in Zenworks. ZENworks- Server properties are empty.
It works fine with Windows XP.
OWS is included Zenworks Agent Version 10.2.0.25097 (The System does not upgrade to other version).
Any Idea for a solution?

Originally Posted by almerola
Hello we have Open Workgroup Suite 2.5 Small Business Edition. With the last automatic update.
Now we have new PC's with Windows7 SP1.
Problem: Windows 7 SP1 does not Register the PC in Zenworks. ZENworks- Server properties are empty.
It works fine with Windows XP.
OWS is included Zenworks Agent Version 10.2.0.25097 (The System does not upgrade to other version).
Any Idea for a solution?
Hi almerola,
If you have maintenance on your NOWS SBE, you should have a link in the NCC to ZCM 11. If you do not see ZCM 11 as one of the items listed, contact the NCC and they will make it available.
You may find your Zenworks questions are answered more quickly in one of the Zenworks forums:

Apply add-on bundle without Zenworks agent installed?

Hi all,
I've created an add-on image file from a bundle within ZCC, but I can't apply it when imaging a computer. It says it can't find any installed Zenworks agent, and that is true, since it is not part of the base image. Instead it gets installed when Windows boots up.
I found this post that says you can use another add-on image to create an empty directory structure on the computer before you apply the add-on image, thus fooling it to believe the agent is installed.
This doesn't seem to work here, though, maybe because we have 64-bit Windows 7. I changed the directory structure to reflect the C:\Program Files (x86)\ folder, but it doesn't seem to work.
Is there any workaround for this, preferrably without having to install the agent within the base image?
Thanks in advance!
Regards,
Pr

Oh well... this was quite silly. I found the answer myself, and it seems that if you only create an add-on image with empty folders, it will not be created on the workstation (although there was no message to indicate that). But when I put a dummy text file into the \Program Files (x86)\Novell\ZENworks\work folder, the structure was created and I was able to push out the add-on image file afterwards without the agent installed.

ZENworks Agent Service stops after deploying 10.3.3 agent.

Hi,
Yesterday i patched our three ZCM-servers (Sles 11) with 10.3.3. I then deployed the 10.3.3 agent to some computers in the IT-department. ZCC shows that the deployment were successful. The problem is that you can not log on to the ZONE from many of these computers. The Novell ZENworks Agent Service stops. I get the following in the Application Windows Log on a Windows 7 64-bit client:
Faulting application name: ZenworksWindowsService.exe, version: 10.3.3.3582, time stamp: 0x4d654308
Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7b325
Exception code: 0xc0000374
Fault offset: 0x00000000000c6ab2
Faulting process id: 0x3f8
Faulting application start time: 0x01cbe3a9dd16f0fc
Faulting application path: C:\Program Files (x86)\Novell\ZENworks\bin\ZenworksWindowsService.e xe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 019eaf5e-4f9e-11e0-986f-005056b925a1
Can anyone help me with this problem?
John Hallberg
Jonkoping University

I would try removing all versions of .NET and then reinstalling the
latest 3.5 SP1 version to see if that helps, since the Agent relies on .NET
If that does not help, I would recommend getting an SR created so the
dump could be analyzed.
On 3/16/2011 5:06 AM, hajo68 wrote:
>
> Hi,
>
> Yesterday i patched our three ZCM-servers (Sles 11) with 10.3.3. I then
> deployed the 10.3.3 agent to some computers in the IT-department. ZCC
> shows that the deployment were successful. The problem is that you can
> not log on to the ZONE from many of these computers. The Novell ZENworks
> Agent Service stops. I get the following in the Application Windows Log
> on a Windows 7 64-bit client:
>
>
> Faulting application name: ZenworksWindowsService.exe, version:
> 10.3.3.3582, time stamp: 0x4d654308
> Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp:
> 0x4cc7b325
> Exception code: 0xc0000374
> Fault offset: 0x00000000000c6ab2
> Faulting process id: 0x3f8
> Faulting application start time: 0x01cbe3a9dd16f0fc
> Faulting application path: C:\Program Files
> (x86)\Novell\ZENworks\bin\ZenworksWindowsService.e xe
> Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
> Report Id: 019eaf5e-4f9e-11e0-986f-005056b925a1
>
> Can anyone help me with this problem?
>
> John Hallberg
> Jonkoping University
>
>
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.

ZENworks agent update from workstation.

Hi there,
Is there a way to get workstations to update themselves automatically with the latest version of the ZENworks agent. (ZCM 11.2.3.a is what we have)
We have a standard image which has a older version of the ZCM agent on it. Images are pulled down and the workstations are automatically built.
Various bundles are then installed automatically on the workstations. When we update the image with other changes etc, we will add the new agent to it.
But until we do that, instead of me having to manually check for all new machines built in the last week / month and then assign the agent update to them,
is there a process, script, bundle of something that can run on the workstation to update the agent itself to the latest version we have.
We are using ZCM 11.2.3a and we need to do this without having to manually visit 200-400 machines.
Thanks
Mark

While I (And Microsoft) recommends configuring your Router/Switches to
pass WOL packets from your trusted WOL Servers (Primaries in this case),
it is also possible to use WOL Proxies to allow this to happen across
your subnets.
There are also some Windows settings that may be necessary to allow WOL
to work from a deep sleep state. I would recommend researching those as
well.
If you are concerned about deploying updates when users are not using
the devices, WOL is something with which I recommend you become more
comfortable using.
On 2/10/2014 8:06 AM, gshaw0 wrote:
>
> craig_wilson;2305537 Wrote:
>> And ask folks to Leave PCs on as well as schedule a WOL task to run for
>> those missed. Then they should all be ready by start of the next school
>> day.
>>
>>
>> On 2/9/2014 3:00 AM, Shaun Pond wrote:
>>> Gshaw0,
>>>
>>> I can't say that it will be non-disruptive, no. Can you not schedule
>>> updates to happen out of hours?
>>>
>>
>>
>> --
>> --
>> Craig Wilson
>> Novell, Inc
>>
>> Any Comments or Posts are only my views and not Novell's
>> Accuracy Attempted but not guaranteed.
>
> 2500 PCs across 5 sites in a couple hundred different rooms, can't
> guarantee even half of them being on. WOL isn't routed across VLANs so
> that won't do the trick either, also not had great experiences with it
> in the past as it seems to rely on machines having had a clean shutdown
> and the socket not being turned off in between (once that happens WOL
> doesn't seem to have any effect until the machine gets a clean startup \
> shutdown cycle)
>
>
Craig Wilson
Novell, Inc
Any Comments or Posts are only my views and not Novell's
Accuracy Attempted but not guarenteed.

How to deploy the Workspace Agent Services as a Window Service!

Hi all,
does anyone know how to install the Workspace Agent Service back as a Windows Service after i re-installed an reconfigured the workspace completly i do not see the Agent anymore in my Windows Services. I sure would like to avoid to have to uninstall and set it up completely again.
The agent start file is located in common\workspacert\9.5.0.0\bin.
Your help is much appreciated
Cheers
André

I hit the same problem after reinstalling workspace.
It seems that the config tool does not create the workspace agent service on subsequent configurations.
A quick search of the configtool.log from the original installation/configuration yields the following:
com.hyperion.avalanche.config.CoreService, INFO, Running command: D:\Hyperion\common\workspacert\9.5.0.0\bin\wksagent.exe -RegService -Auto -Name HyS9Core1 -DisplayName Hyperion Workspace - Agent Service -Description HyS9Core1, Provides service infrastructure to run services locally
Dropping the above line at the command prompt fixed the issue for me.
Cheers,
Aaron
Edited by: user8871938 on 15-Feb-2010 06:56

Remote Agent for ACS for Windows 2008 R2 64-bit

Hi,
We having difficulties with installing remote agent on windows 2008 R2 64-bit server and got the attached error.
Our ACS is 4.2.0.124 and remote agents we tried are :Remote-Agent-ACSse-win-v4.2.1.15-K9.zip and Acs-4.2.1.15.9-RA.zip.
I see following urls says it does not support Windows 2008 R2 and also 64-bit Windows,
https://supportforums.cisco.com/message/3135061#3135061
http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_for_solution_engine/4.2/installation/guide/remote_agent/rawi.html#wp289019
However following url says its support 2008 R2 with 64-bit version
http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_for_windows/4.2.1/Release_Notes/acs421_rn.html
Appreciate if someone can adivse us what vesion (file name) of Remote Agent can support (or working) for Windows 2008 R2 64-bit.
thanks in advance

Hi Tarik,
What I wanted to say that the below url says that ACS 4.2 does not support on 64-bit OS:
ACS Requirements
You must use ACS Remote Agent for Windows, version 4.2, with ACS SE, version 4.2. We do not support other Cisco Secure ACS releases.
Note ACS Remote Agent 4.2 for Windows does not support 64-bit operating systems.
http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_for_solution_engine/4.2/installation/guide/remote_agent/rawi.html#wp289019
However could you please let me know what exact Remote Agent file you recommend to use for windwos 2008 R2 64-bit Server. The ACS SE version that I have is 4.2.0.124.
Thanks

Zenworks Agent interferes with GroupWise & Messenger

We have been running GW 8 and IM 2.0.4 without issue for several months on XP machines along with Zenworks 7. We recently upgraded to Zenworks 10.2 and since then we have had numerous users complain that GroupWise and/or Messenger hangs on them. We find in these cases that there are a number of instances of GroupWise in the task manager and upon killing the processes, Messenger will begin working again and GroupWise can be started again without a problem. However, over time the same thing will occur again. The surefire thing we have found to prevent it from happening is to remove the Zenworks agent from the machine.
Anybody else having issues with the Zenworks 10.2 agent interfering with GroupWise and Messenger?

Originally Posted by whoppe
We have been running GW 8 and IM 2.0.4 without issue for several months on XP machines along with Zenworks 7. We recently upgraded to Zenworks 10.2 and since then we have had numerous users complain that GroupWise and/or Messenger hangs on them. We find in these cases that there are a number of instances of GroupWise in the task manager and upon killing the processes, Messenger will begin working again and GroupWise can be started again without a problem. However, over time the same thing will occur again. The surefire thing we have found to prevent it from happening is to remove the Zenworks agent from the machine.
Anybody else having issues with the Zenworks 10.2 agent interfering with GroupWise and Messenger?
We have no issues with GW on workstations running ZCM10.2. We don't use messenger so maybe the messenger is causing this issue.
Thomas

Strange behavior of Windows Azure Compute Emulator (SDK 2.3)

Today, after an update of the Azure SDK from 2.2 to 2.3, I noticed that only one of the two instances of my web role is started in
the Azure Compute Emulator, the output of the Start-AzureEmulator is this:
VERBOSE: Starting Emulator...
VERBOSE: Role is running at http://127.0.0.1:81/
Role is running at tcp://127.0.0.1:3389/
Role is running at tcp://127.0.0.1:3389/
VERBOSE: Started
and only one instance is started in the Azure Compute Emulator.
But in the past was something similar to this one:
VERBOSE: Starting Emulator...
VERBOSE: Role is running at http://127.0.0.1:81/
http://127.0.0.1:82/
Role is running at tcp://127.0.0.1:3389/
Role is running at tcp://127.0.0.1:338/
VERBOSE: Started
and two instances were started.
I already found this thread:
http://stackoverflow.com/questions/13946634/strange-behavior-of-windows-azure-compute-emulator-sdk-1-8-with-multiple-role
but it was not useful in my case (Microsoft.WindowsAzure.Common.WorkArounds.BindToAllIpsWorkAroundEnabled is False).
Thanks in advance for any help.
OS: Windows 8.1
Azure SDK: 2.3
Azure Compute Emulator: 2.3.0.0

Hi,
As far as I know, powershell didn't have a parameter to start azure emulator with full express, please try to use Command-line to test, refer to
http://msdn.microsoft.com/en-us/library/gg433130.aspx for more details, if this didn't give you help, please feel free to let me know.
Best Regards,
Jambor
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

WM_CAP_DRIVER_CONNECT strange behavior on Windows 7

Hi,
I'm sorry if this is not the right place to post my question, but I did not found one, maybe someone could suggest me.
Anyway, I have some code for aquiring cam image using WM_CAP* messages.
While it works perfectly on an XP machine, in Seven I have a lot of strange behavior.
On the first call to
SendMessage(hCapWnd, WM_CAP_DRIVER_CONNECT, DriverIdx, 0&)
The "source Video" window appear, while on XP it return immediately true.
Now I choose the source and I press OK but the SendMessage returns false!
I try again and this time no window appear and the acquisition start normally!
Then, I disconnect the driver and I try to connect again but the windows appear every time and SendMessage returns false!!!
It make me crazy!! Please, could someone have some suggestions?
Regards,
Daniele.

Daniele, I'm fighting the same problem as yours. I gave up at the first call to capDriverConnect. Didn't know it may succeed at the second shot.
GetLastError reports 0 = ok.
But there must be a way to succeed, because I started an app attached to the driver I use, and it works correctly, without the unwanted dialog. Can't check it right now, but it is probably the same app as here (if link does not work, just search for vbvidcap):
http://www.natech-inc.com/names/other_programs/vidcap/index.html
How does it go in your case?
edit1: Sometimes there are problems if a window belongs to a different thread. Are you sure you call capDriverConnect from the thread that created the window with capCreateCaptureWindow?
edit2: Sorry for the wrong hint. vbvidcap has the same problem. The app that works uses directshow, not vfw.
edit3: Maybe the camera is reserved by some other application, or by unknown bug. Appearing of the "choose source" dialog is a sign of the blockage of the device, this works so on XP. In my case I resolved the problem by unplugging the camera and connecting
it again. And the drivers must be ok. So I remain a believer of VFW :) Troublesome and awkward, but works!

Zenworks Agent Windows 7 64

Hello.
I install Zenagent 7.0.1.4 on a laptop running Windows 7 64. It seems to install fine but upon login I do not get any desktop icons and does not create a workstation object in ConsoleOne.
Any Ideas?

Originally Posted by spond
JebediahShapnacker,
there is no support whatsoever for ZDM7 on Windows 7, I'm afraid...
Shaun Pond
I appreciate that their is no support but was hoping that someone might come across this issue and resolved it. I have installed it on Win7 32bit a few times and it works fine.
Thanks

Device Name Sporadically Changing ZENworks Agent Properties

I'm having a problem with a few Dell Windows 7 machines using ZENworks Configuration Management (ZCM) 10.3.4 client.
The problem is the device name, in the ZENworks Adaptive Agent Properties, is sporadically changing and reassigning with other device names and sharing the device name with another computer.
All the machines have been built from a single image, using R-Drive Image software, with the ZCM client already built-in to the image.
In attempt to resolve the problem, I've uninstalled the ZCM client, CASA as well as deleting the device name from the Zenworks Control Center (ZCC).
Re-installed the ZCM client and again received a different device name of a different workstation.
I've already tried using Zenworks AgentCleanup tool to remove the ZCM client and deleted the device name from the ZCC, but it did not resolve the problem.
I can only assume the problem lies within the image compiled with the ZCM client. How do I stop this from continually happening and make the ZCM report the correct device name and if possible, without having to create a new image?

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

Zenworks Agent 10.3.3 - Windows 7 32 -Strange behavior

Similar Messages

Maybe you are looking for