Re-registering a Workstation..

Dear All,
I have done a Zen app to Re-register Workstations (we use Zen 6.5, Netware 6.5 , XP SP2 desktops). On our PCs in the host file we have a line which has the "IPaddress of the Zen Import Server Zenwsimport".
Is there a way for me to take this line out using some kind of a script. The only problem is the IPAddress could be anything, so ideally what I want it some script to go and search for the word "Zenwsimport" and delete it, then I can insert the correct IP.
Any help much appreaciated.
Thanking you in advance.
Varuni

Populate this Registry Key.................
HKLM\Software\Novell\ZENworks\zenwsreg,ImportServe r=xxx.xxx.xxx.xxx (or DNS)
This will over-ride the DNS/Host File Settings and is Easier to maintain for
obvious reasons ;>>
"Varuniw" <[email protected]> wrote in message
news:[email protected]..
>
> Dear All,
>
> I have done a Zen app to Re-register Workstations (we use Zen 6.5,
> Netware 6.5 , XP SP2 desktops). On our PCs in the host file we have a
> line which has the "IPaddress of the Zen Import Server Zenwsimport".
>
> Is there a way for me to take this line out using some kind of a
> script. The only problem is the IPAddress could be anything, so ideally
> what I want it some script to go and search for the word "Zenwsimport"
> and delete it, then I can insert the correct IP.
>
> Any help much appreaciated.
>
> Thanking you in advance.
> Varuni
>
>
> --
> Varuniw
> ------------------------------------------------------------------------
> Varuniw's Profile: http://forums.novell.com/member.php?userid=4263
> View this thread: http://forums.novell.com/showthread.php?t=363035
>

Similar Messages

Application Explorer won't start unless logged into workstat

Since upgrading all our XP workstations to Zenworks Desktop Management Agent to 7.0.173.90519 (Zenworks7 Sp1R4) some computer's Application Explorer is failing to start properly.
The Application Explorer system tray icon is defective, it does not respond to anything and no application folders are loaded. However it does work ok if you use Workstation Only first then log into Edirectory afterwards
I have tried reinstalling the Desktop Management client, Novell Client, re-registering the workstation and clearing the NAL Cache. The only thing that fixes it is reloading Windows

If you are able to open an SR, I would recommend doing so.
What happens if you set "Application Explorer" so that is does NOT load
automatically.
Login Normally.
Then load "Application Explorer" manually.
If that helps, how are you loading "Application Explorer".
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.
"Patrick Farrell" <[email protected]> wrote in message
news:YvXFm.357$[email protected]..
> neil france wrote:
>> Since upgrading all our XP workstations to Zenworks Desktop Management
>> Agent to 7.0.173.90519 (Zenworks7 Sp1R4) some computer's Application
>> Explorer is failing to start properly.
>>
>> The Application Explorer system tray icon is defective, it does not
>> respond to anything and no application folders are loaded. However it
>> does work ok if you use Workstation Only first then log into Edirectory
>> afterwards
>>
>> I have tried reinstalling the Desktop Management client, Novell Client,
>> re-registering the workstation and clearing the NAL Cache. The only
>> thing that fixes it is reloading Windows
>>
>>
> Sounds like you're having the same issue that I am having. See the
> thread "ZFD agent hangs after splash screen". Please post there so that
> Jared can get info from you as well to determine if it's the same issue.
>
>

ZCM 10.3.3 - cannot register new installations

This is a problem that recently has reared its ugly head. Installing ZCM 10.3.3 agent on XP Pro SP3 workstations appears to work; however, the workstations do not register with the ZCM server. Newly imaged workstations (with ZCM 10.3.3 installed some time ago) register automatically. Taking a known-good machine, I can "zac unr" and "zac reg ..." with success. Yet, installing ZCM today on a fresh computer, I can't register the workstation.
I cannot think of what changed or exactly when this week this problem started. The machines that had ZCM 10.3.3 installed prior to this problem starting are behaving properly. I can unregister and reregister without failure.
"zac cc" followed by "zac reg https://zcm.domain.tld" returns the following error:Unable to register with the server at: https://zcm.domain.tld.
Service Error. code: -21, message: Could not determine device type from <OS> tag: unsupported
The log file includes the following, which makes me think the pre-agent installer didn't install the sqlite stack:[DEBUG] [07/28/2011 14:35:41.968] [1912] [ZenworksWindowsService] [19] [] [ZenCache] [] [Exception getting object record for key ZoneConfig:Realms
Type: System.DllNotFoundException
Message: Unable to load DLL 'sqlite3': The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3)
Stack Trace:
at Novell.Zenworks.Cache.Sqlite.Sqlite.sqlite3_open(S tring dbname, IntPtr& handle)
at Novell.Zenworks.Cache.Sqlite.SqliteConnection.Open ()
at Novell.Zenworks.Cache.SqliteEntryInfoProvider.GetO bjectEntry(String key, UserContext owner)
Any ideas on what I should do?
Thanks,
Eric

Originally Posted by epoe
This problem has been resolved.
I had some funky files in the Windows Side-by-side folder that were artifacts of a previous wonky install of a different application. I had experienced issues with these specific files before that were resolved by removing them; they just weren't removed from these images that I was doing the upgrade from Zen 7 to ZCM 10.
After removing these two files, ZCM was able to be registered without error.
For the morbidly curious, the two files I removed are:
c:\windows\WinSxS\Manifests\x86_Microsoft.VC90.CRT _1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_6f74963e.manifest
c:\windows\WinSxS\Policies\x86_policy.9.0.Microsof t.VC90.CRT_1fc8b3b9a1e18e3b_x-ww_b7353f75\9.0.30729.1.policy
I have to ask, how did you figure out that those files were related to a previous zenworks install? I had the same issue, but didn't have the same files. They were close in name, but then I was installing 10.3.4, not 10.3.3. I removed the two files, the manifest had a different number at the end, but the policy file was the same name. Thank you so much for that tip, it saved me a few hours of head scratching and saved the customer from a re-image.

Workstation Name

Zen 3.2 sp3/Netware 5.1 sp7/Windows 9x PC's
Importing workstations is working fine except for a naming anomaly. We
are using ComputerName + MAC as the object name, and when registered,
the workstations name registers as the name of the original image, not
the actual computer name.
Here is the scenario:
LabPC01 is our master image. We then put that image on the other 9 (or
however many) PC's in a lab, and rename the PC's to LabPC02,
LabPC03...LabPC10.
Upon Registering the PC's all ten register with the correct MAC address,
but with the wrong name:
LabPC01 00:02:03:04:05:AF
LabPC01 00:02:03:04:0B:D4
LabPC01 00:02:03:04:B5:FA
LabPC01 00:02:03:04:22:AB
I have searched the registry, and the only place the old name appears is
in the key HKEY_CURRENT_USER\Software\Microsoft\Windows
Media\WMSDK\General\ComputerName
I apologize if this information is readily available in the
documentation, but I am trying to determine where the Zenworks
Registration process gets the computer name from so that I can ensure
future workstations import with the correct name. My first guess was
that the key above must be the place, but I was not sure why the name
would come from this location. (Note this problem exists only in Win
9x, not XP).
Thanks for any insight.
Daryl

My guess is that the Workstation is Registering prior to a technician
actually renaming the PC.
As part of the procedures for deploying the PC, I would run "UNREG32.EXE" at
the same time the workstation is renamed.
DT wrote:
> Zen 3.2 sp3/Netware 5.1 sp7/Windows 9x PC's
>
> Importing workstations is working fine except for a naming anomaly. We
> are using ComputerName + MAC as the object name, and when registered,
> the workstations name registers as the name of the original image, not
> the actual computer name.
>
> Here is the scenario:
> LabPC01 is our master image. We then put that image on the other 9 (or
> however many) PC's in a lab, and rename the PC's to LabPC02,
> LabPC03...LabPC10.
>
> Upon Registering the PC's all ten register with the correct MAC address,
> but with the wrong name:
> LabPC01 00:02:03:04:05:AF
> LabPC01 00:02:03:04:0B:D4
> LabPC01 00:02:03:04:B5:FA
> ...
> LabPC01 00:02:03:04:22:AB
>
> I have searched the registry, and the only place the old name appears is
> in the key HKEY_CURRENT_USER\Software\Microsoft\Windows
> Media\WMSDK\General\ComputerName
>
> I apologize if this information is readily available in the
> documentation, but I am trying to determine where the Zenworks
> Registration process gets the computer name from so that I can ensure
> future workstations import with the correct name. My first guess was
> that the key above must be the place, but I was not sure why the name
> would come from this location. (Note this problem exists only in Win
> 9x, not XP).
>
> Thanks for any insight.
>
> Daryl
Craig Wilson
CNE3, 4, 5 - MCSE - CCNA
NSC Sysop (http://support.novell.com/forums/)
Tech Writer - http://www.ithowto.com
(I Peter 4:10)

Trouble importing workstations

I am in the process of setting up remote control. I am having a
problem
importing the workstation. I get the following error:
*****(4)***** 04/02/03 03:43:05 pm
WSREG-v3.0 This log file is reporting activity on a
WM_USER_LOGIN_EVENT
event.
WSREG-v3.0 Registering the workstation failed with an error 34970.
What does this mean?

Here is the deal......
I have a school with 6 different campuses. I am trying to get all the
computers at the respective campus to register with that campuses
server and
container.
One campus works fine. I am getting this error on one of the other
campuses. The workstation is a Windows 98 SE machine.
Can you have machines register with different containers? I have
force run
a host file that the ip address is different for the zenwsimport
entry.
"Timothy Leerhoff" <[email protected]> wrote in message
news:mPMia.36534$[email protected]..
> Do one or all PCs have this error?
> What OS is on the PCs with the error?
>
> If only a few try running UNREG32.EXE the try registering them
again.
>
>
> --
> Timothy Leerhoff
> Principal Consultant
> Independent Experts
> Novell Support Forums Sysop

Certificate update / workstation registration

Hi there
I will be updating the certificates on the zenworks servers. These have been signed by the eDir external CA.
I will apply the certificate,then refresh all devices and thereafter enforce the certificates.
My question is, we have a number of images which we deploy to various labs/workstations.
The agent has already been installed on these workstations and then the agent was
cleaned up prior to uploading it to the server.
So the images created earlier in the year are not aware of the new certificate changes.
When the image is deployed we tftp a few scripts to the workstation which then registers the workstation in the zone.
My question is now that the certificates have changed I need to do a zac retrust.
Do I register the workstation and then run the retrust or do I run the retrust and then register the workstation ?
Or is there another / better way to do this.
Thanks
Mark

Assuming your images have old certs, when you deploy them I suspect all
you will need to do is run a "zac reg" command.
A prompt to accept the cert will appear unless you also script trusting
the new CA prior to running the reg command.
As others noted, you may want to tweak your image.
In this case, simply update the "initial-web-service" file in your image
from a device that has the updated CA trust.
On 9/23/2014 4:46 AM, markvh wrote:
>
> Hi there
>
> I will be updating the certificates on the zenworks servers. These have
> been signed by the eDir external CA.
>
> I will apply the certificate,then refresh all devices and thereafter
> enforce the certificates.
>
> My question is, we have a number of images which we deploy to various
> labs/workstations.
> The agent has already been installed on these workstations and then the
> agent was
> cleaned up prior to uploading it to the server.
> So the images created earlier in the year are not aware of the new
> certificate changes.
>
>
> When the image is deployed we tftp a few scripts to the workstation
> which then registers the workstation in the zone.
>
> My question is now that the certificates have changed I need to do a zac
> retrust.
> Do I register the workstation and then run the retrust or do I run the
> retrust and then register the workstation ?
>
> Or is there another / better way to do this.
>
>
> Thanks
> Mark
>
>
Going to Brainshare 2014?
http://www.brainshare.com
Use Registration Code "nvlcwilson" for $300 off!
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer
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.

Wrong workstation registration

Why sometimes a WS is registrered on the wrong container?
(on the WS container of another server/site)
Using NW5.1SP5, ZfD3.2SP2
Thanks in advance
Ricard

> Why sometimes a WS is registrered on the wrong container?
> (on the WS container of another server/site)
> Using NW5.1SP5, ZfD3.2SP2
>
> Thanks in advance
>
>
> Ricard
>
>
>
>
>
Your workstaion import policy(s) dictate(s) where the workstations
will be imported into. If for example you have the policy set to import
into the USER Container, that is where it will go [The user container that
successfully registered the workstation]. Many times this could be the
container of technician that setup the PC and not the end user because you
may have to reboot a few times while installing applications, which runs
WSREG32.exe.
To resolve this, you need to run UnReg32.exe from the SYS/Public
folder and allow the end user to log in and register the workstation.
If you have more than one policy, you may consider utilizing only one
for easier administration.
Hope that helps

Workstation Inventory - java.lang.OutOfMemoryError

I'm getting an error on my server when it tries to do inventory of
workstations.
Mar 21, 2005 1:07:44 PM Created workstation:
ssmith.Workstations.ARDELT.FACS
java.lang.OutOfMemoryError
I believe the TID below describes the problem. Any word on a
resolution?
http://support.novell.com/cgi-bin/se...?/10097015.htm
Thanks, Oksana

I believe I may have found the problem.
see:
http://support.novell.com/cgi-bin/se...?/10094436.htm
Thank God for Novell's support site... it's a life-saver, and of
course, to all you providing us with additional support and guidance
(not to mention - hand-holding!)
Oksana
On Tue, 22 Mar 2005 19:30:53 GMT, Oksana
<[email protected]> wrote:
>We want to use the agent that goes with ZENworks 6.5 sp1. We have
>about 25 workstations already using it - the remainder of agents are
>older 300+.
>
>Oksana
>
>On Tue, 22 Mar 2005 19:27:01 GMT, Oksana
><[email protected]> wrote:
>
>>When we try to register a workstation using zwsreg manually in a
>>command prompt window - the prompt doesn't come back or we get an
>>error if the server is already reporting the error.
>>
>>We can't register a workstation, so no inventory can be done nor no
>>applications can be delivered to the workstation since users have
>>limited rights under Windows XP.
>>
>>The error appears on the ZENworks Workstation Import screen.
>>Sorry I wasn't more clear.
>>
>>Oksana
>>
>>On Tue, 22 Mar 2005 18:46:20 GMT, Marcus Breiden
>><[email protected]> wrote:
>>
>>>On Tue, 22 Mar 2005 17:25:16 GMT, Oksana wrote:
>>>
>>>> We've started to rollout out the newest agent for ZENworks 6.5 sp1 but
>>>> can't re-register workstations. This is a huge problem since we're
>>>
>>>but you are talking about inventory... what does inventory to do with the
>>>upgrade..
>>>
>>>please try aat least ir5 on the inventory... if possible ir6

Workstation Manager - NCP requests - server utilization

Dear experts,
My apology for the long question... but we're kinda stuck here.
We're having a problem with high utilization on our server that seems to be
caused by NCP requests made by Workstation Manager on some machines.
After upgrading to Client 4.90SP1a and rolling out ZEN4 Agent
4.00.1093.40329 (previously on 4.83SP1, no ZEN4 Agent), we're getting high
utilization (~80%) on our file server which normally sits under 15%
utilzation. Network Monitor records between 18k-60k packets/second.
Packet capture shows that a number of machines (about 10% of them) keep
sending this request :
NetWare Core Protocol
NCP over IP signature: Demand Transport (Request) (0x446d6454)
NCP over IP length: 30
NCP over IP Version: 1
NCP over IP Reply Buffer Size: 391
Type: Service request (0x2222)
Sequence Number: 137
Connection Number: 15
Task Number: 4
Function: 22 (0x16), Get Extended Volume Information
Packet Length: 5
SubFunction: 51 (0x33)
Group: File
Volume Number: 4
on which the server replies with :
NetWare Core Protocol
NCP over IP signature: Transport is NCP (Reply) (0x744e6350)
NCP over IP length: 16
Type: Service reply (0x3333)
Sequence Number: 137
Connection Number: 15
Task Number: 4
Response to Request in Frame Number: 2629
Time from Request: 0.000731000 seconds
Function: 22 (0x16), Get Extended Volume Information
SubFunction: 51 (0x33)
Completion Code: 251 (0xfb), Attempt to use an invalid parameter (drive
number, path, or flag value) during a set drive path call
Connection Status: 0
Server facts :
Novell NetWare 6, Support Pack Revision 05
Server Version 5.60.05 May 27, 2004
Novell eDirectory Version 8.6.2 SMP
NDS Version 10350.30 December 15, 2003
ZENworks for Desktops 4.0.1
Workstation facts :
- only Windows 2000 machines do this, XPs are fine.
- Novell Client 4.90SP1a
- ZEN 4 Agent 4.00.1093.40329
On problem workstations, the following symptoms are observed :
- Workstation Manager showing high utilization
- Policies are not showing up on Workstation Manager Scheduler
- ZENWSIMPORT is pointing to the correct import server as per HOSTS file
Access right to the Volume Number 4 (as shown in the packet capture) is not
a problem, both for users and for workstations. One thing we notice
though, the NCP request was made from a NOT-LOGGED-IN connection.
At one stage we had similar high utlization problem - and the workaround to
this was by giving [RF] rights to Public, which is of course, less than ideal.
These has been attempted on problem workstations :
- unregistering workstation using zwsreg -unreg
- deleting workstation object from ConsoleOne
- registering the workstation using zwsreg
- applying SP4 for Windows 2000
The problem is that there is no consistent result. On some, getting the
workstation registered properly seem to fix the problem. However, on
others even when a workstation object is OK, some are still getting high
utlization on Workstation Manager and still sending NCP requests.
Any suggestions to point me to the right direction?
Thanks in advance,
Andre
[email protected]

> - only Windows 2000 machines do this, XPs are fine.
Sorry, just found out 2 XP machines are also sending NCP requests... :(

"ZENNW32.DLL is misssing the entry point nwappLoadOD."

We are getting the error
"ZENNW32.DLL is misssing the entry point nwappLoadOD."
I have found this in some other threads in this forum, but they did
not go
in a useful direction for me. This error message is appearing on a
WinXP Pro
workstation before the NWgina appears after boot up. Zen policies are
not
working.
The history of this error is that we installed SP1b on ZfD 4. We thenupdated our workstations from client 4.83 to 4.9 and afterwards the
Zen
agent to the MSI version shipping with SP1b. I have tried deleting the
installpath registry key as suggested in TID 2967507 and also followed
the
other suggestions. No luck. I also think I got the same error at some
point
after rolling back from 4.9 client to 4.83, without updating the
agent.
ZfDagent.msi will install fine on a clean machine that has not had the
previous version of the agent or client installed and policies will
work.

> interesting, someone else has reported this problem, but it looked like
> a terminal server issue.
I also found a few thread with this on the forum, but they were with
Win98 or 2k on the workstations, and we have XP, so the client is
different. Also, their problem was different, and the error message about
the missing entry point was just another one of their symptoms. My
problem is that the agent is not working on my XP workstations and I
cannot apply policies or register a workstation (which I can do with the
new wstations where we never had client 4.83 or the Zfd4 agent installed,
and also on our Win98 workstations).
> I'm still not clear on the exact sequence;
Ok, we had client 4.83 and Zfd4 installed. All was well re policies etc.
We updated to SP1b with Zfd, then we updated all our clients from 4.83 to
4.9. Then we deleted the InstallPath key in the registry, uninstalled the
Zfd4 agent and installed the .msi version tht comes with SP1b.
> If so, what options did you choose with client 4.9 during install?
The tech who did the client upgrade tells me that when she did a custom
install of 4.9 (with the old management agent present), she didn't get
the ZfD options in the client she used to get with 4.83. There was only
one box which was ticked and greyed out (i saw this too when I was
playing around). But I have since discovered, that when I took the
management agent off and then uninstalled 4.83 and installed 4.9, I had
all the ZfD options to tick I had with 4.83.
> Have
> you tried 4.9sp1a?
We did try it on a few machines, but found that a staff member who logs
in on lab machines as xxxxx.staff could not log in on the patched
clients. When we put the 'staff.' into the context field in the advanced
section of the login and only his username at the top, it worked! We
tried this on all the patched client machines and it happened on all of
them (I won't be upset if you don't believe me, it's too weird for
words!).
I'll try patching the client and see what happens when I update to
the .msi agent.
Thanks for your help, Shaun.
Renate
>

Uninstall/reinstall Agent

Hi,
Running ZCM 11sp1a on Suse11sp1 64 bit.
I need to uninstall/reinstall the agent on a Linux 11sp1 server. When
installing the agent I get a message back saying the agent is already
installed. If I run "zac reg -g https://zenserver.domain" I get an "Unknown
error while communicating with ZENworks Management Daemon"
So, two question ... How do I remove the Zen agent and using the "zac reg"
command how would I re-register any workstation agent to a new zone?
Regards
John

John,
uninstall is here http://www.novell.com/documentation/...a/bon1lbl.html
Shaun Pond

Import policy error

I am getting the following error when I do a zwsreg -importpolicy with my
clients.
Zenwsreg returned the following error code: 404
When I looked up the error on Novell I didn't come up with anything. Anyone
have any idea on what this might be?
Thanks
Rich

I actually have a batch file that runs during part of the login to Novell.
It has the following lines in it.
@echo on
zwsreg -unreg
zwsreg -importpolicy "LHSOffice:General:Workstation
Import.policys.lhs.usd405"
It unregs the system just fine but doesn't want to register the workstation
to the correct policy. I have a workstation container with three sub
containers for each group I want to register to.
>Workstations\
>Office\
>Students\
>Teachers\
The policies will push the workstation in the correct folder so that my
laptops are getting the correct policies and applications depending on who
owns the laptop.
I have had nothing but problems with this setup and am looking at a better
way to get this setup. I might only have a fraction of the laptops (and I
have around 650 district wide) to register into zenworks.
When I installed the ZENagent I didn't specify a middle tear server. The CNE
that helped me said I didn't need it and that it wasn't installed. Could
this be causing my problems. We are a Novell shop at this point.
NetWare 6.5 SP5
Zenworks 6.5 SP2
Thanks
Rich

WM_User_Login_Event & Winsock connect () failed. errors

I am running zen 3 and up until the last week or so I have had no
problems registering my workstations in console one. But now I am
suddenly getting the following error message in the wsreg32.log file
when I try to register a new machine:
*****(1)***** 08/12/04 02:23:12 pm
WSREG-v3.0 This log file is reporting activity on a
WM_USER_LOGIN_EVENT event.
WSREG-v3.0 While contacting the Work Station Import Service, an error
-1 was encountered, and error description <Winsock connect() failed.>
was reported.
WSREG-v3.0 Registration will not occur for this event.
WSREG-v3.0 The program finished running.
When I look in console one the workstation is not registered.
I am using client 4.9 sp1a with the update on my workstations.
Any help will be appreciated.
Thanks,
Susan

Hi Susan,
- Have you checked if the Workstation Import service on the server is up
and running?
- Are you able to ping ZENWSIMPORT from the new machine? is it pointing to
the correct IP address (the import server)?
Hope this helps.
Andre
[email protected]
> I am running zen 3 and up until the last week or so I have had no
> problems registering my workstations in console one. But now I am
> suddenly getting the following error message in the wsreg32.log file
> when I try to register a new machine:
>
> *****(1)***** 08/12/04 02:23:12 pm
> WSREG-v3.0 This log file is reporting activity on a
> WM_USER_LOGIN_EVENT event.
> WSREG-v3.0 While contacting the Work Station Import Service, an error
> -1 was encountered, and error description <Winsock connect() failed.>
> was reported.
> WSREG-v3.0 Registration will not occur for this event.
> WSREG-v3.0 The program finished running.
>
> When I look in console one the workstation is not registered.
>
> I am using client 4.9 sp1a with the update on my workstations.
>
> Any help will be appreciated.
>
> Thanks,
> Susan

Running zwsreg.exe as an app object or schedule that runs everytime nal refreshes.

Hi,
I'm not a 'heavy' novell user. I do the lower level things. But
here's my problem that I can't for the life of me figure out.
Our workstation registration process runs on login. It will remove the
workstation every 40 days. It is a large manufacturing fascility.
Many of the tools don't allow the workstations to log out and back in
within that time frame.
I'm trying to figure out a way to 'schedule' the zwsreg.exe to run as a
normal user in the background and unregister if it's registered, then
register the workstation so we can remote connect to them without
running into workstations that have become 'unregistered'. I can run
the zwsreg from the command line easy enough. But it seems there are
problems with either mapping or file rights when i try to put it in a
batch file or run it right as an app object. Has anyone ran into this
situation before and found a solution?
I'd have no problem I guess using the workstation scheduler, but that
doesn't have rights when a user is logged in to register :(
Thanks,
Bill w.

Do you have these shop floor workstations under a separate workstation
policy? You could add a "Scheduled Action Policy" for those workstations
with zwsreg as the action, and schedule it to run, say weekly.
Or you could just move those workstations into a different container that
the workstation removal policy doesn't specify... that way the won't be
removed every 40 days... or ever.
-Adam

NalView restart on windows

I want to exit novell Application Launcher with dos script shell.
I kill NALAgent.exe (taskkill /F /IM NalAgent.exe /T) but icon tray is always up
I kill NALNTSRV.exe (taskkill /F /IM NALNTSRV.EXE /T) but icon tray is always up
I stop Workstation Manager service (net stop ZFDWM) but icon tray is always up
I can close it with a right click on windows desktop.
How can I do it ?
My objective is to restart it : stop and start. Because I modify the registry.
this is the script
net stop ZFDWM
taskkill /F /IM NalAgent.exe /T
taskkill /F /IM NALNTSRV.EXE /T
reg ADD HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZEnWorks\Zenwsr eg /v ImportServer /t REG_SZ /d {IP_SERVER} /f
reg ADD HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZEnWorks\Zenwsr eg /v Importws /t REG_SZ /d %COMPUTERNAME%.{OU_TARGET} /f
reg ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstatio n Manager\Identification" /v "Workstation Object" /t REG_SZ /d %COMPUTERNAME%..{OU_TARGET} /f
reg DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstatio n Manager\Identification" /v "Workstation ID" /f
net start ZFDWM
"C:\Program Files\Novell\ZENworks\NalView.exe"
NAL agent 7.0.1.4

If all your doing is re-registering the workstation, why not just:
nalwin32 /U (unloads the NAL)
zwsreg -unreg (unregisters workstation, removes info locally, which
should include those reg entries)
make your changes
zwsreg
not sure if you really need to restart the workstation manager.
>>> On 3/2/2010 at 9:36 AM, in message
<[email protected]>,
lebobinnec<[email protected]> wrote:
> I want to exit novell Application Launcher with dos script shell.
>
> I kill NALAgent.exe (taskkill /F /IM NalAgent.exe /T) but icon tray
> isalways up
> I kill NALNTSRV.exe (taskkill /F /IM NALNTSRV.EXE /T) but icon tray
> isalways up
> I stop Workstation Manager service (net stop ZFDWM) but icon tray
> isalways up
> I can close it with a right click on windows desktop.
>
> How can I do it ?
>
> My objective is to restart it : stop and start. Because I modify
> theregistry.
>
> this is the script
>
> net stop ZFDWM
> taskkill /F /IM NalAgent.exe /T
> taskkill /F /IM NALNTSRV.EXE /T
> reg ADD HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZEnWorks\Zenwsr eg
> /vImportServer /t REG_SZ /d {IP_SERVER} /f
> reg ADD HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZEnWorks\Zenwsr eg /vImportws
> /t REG_SZ /d %COMPUTERNAME%.{OU_TARGET} /f
> reg ADD
> "HKEY_LOCAL_MACHINE\SOFTWARE\Novell\WorkstationMan ager\Identification
> " /v "Workstation Object" /t REG_SZ /d%COMPUTERNAME%..{OU_TARGET} /f
> reg DELETE
> "HKEY_LOCAL_MACHINE\SOFTWARE\Novell\WorkstationMan ager\Identification
> " /v "Workstation ID" /f
> net start ZFDWM
> "C:\Program Files\Novell\ZENworks\NalView.exe"
>
>
> NAL agent 7.0.1.4--
lebobinnec------------------------------------------------------------------
------lebobinnec's Profile:
> http://forums.novell.com/member.php?userid=79927View this thread:
> http://forums.novell.com/showthread.php?t=403440

Re-registering a Workstation..

Similar Messages

Maybe you are looking for