Search results for query: *

Glad that you sorted it out. Have a great Christmas Zen Ad maora ultra vitam

Slink, Ensure that teh workstation is registerred and that the policy is in effect on the workstations container. Also ensure that the group policies being used are the exported XP ones. Check the GP*.txt files at the root of C:\drive for errors. Zen Ad maora ultra vitam

Actually, sounds like the other containers clients have the zenworks software installed (in client 32). These will naturally look for the zenwsimport service within DNS (or Hosts). Once the zenwsimport service is found, then the server package applicable to the server comes into effect which...

Just go into the policy package, select windows group policy (properties) and then click on edit. All pops up infront of you and then edit to your hearts content. Zen Ad maora ultra vitam

Reilli, You don't need to re-install ZFD, just take a copy of the snap-in's directory under sys:\public\mgmt\consoleone\1.2\ and copy to your local machine. To see whether ZFD is installed correctly on teh server, type in java -showall at the system console and verify that the services...

Errors will come up on the client side machines and there will be a delay in startup (whilst services are sought, notably the zenwsimport service - ordinarily hosted on the root zenworks server). Other than that, should be okay so long as no local nalwin32 exists in the startup folder. Shame to...

Sure. Basically, when Client 32 is installed, the zenworks features need to be selected. Once they are, the various components are installed and become part of the users Operatational OS. Services such as ntsvrldr etc. are run. The options you have are to manually disable these services or, much...

AceAl, I have rolled this out to a large international client and can state that all components barring the extensible policies and security policies are fully functional. XP imaging is not officially supported, but I have not had a problem with it. To answer your question, basically, the XP...

My first question has to be, "Why are you removing ZenWorks?!!!" You don't have to answer that one! Basically, in removing ZenWorks, the only impact to the tree will be in terms of the schema, which has been extended to permit the ZenWorks components. My advise to you, if you are...

Performer, Ensure that in the start menu under startup, there is no local reference to the nalwin32.exe. If there is and your local NALcache is not populated, you will not see anything. If this component is correct, ensure that the appropriate OS has been set for availability. If this is also...

What is the service pack release that you are using? I am using SP3 at the moment and everything is sweet. With ZFD, u need to be doubly careful about the process that you follow re: upgrading JVM and application of service packs and, strangely enough, the version of console one that you are...

Should be consistent across NT4, W2K and XP, generally to do with rights...er...I mean permissions :-) Zen

Dude, Your best option is to scrap client 4.81, rollout 4.83 (applying the service patch for NWFS). Then, also ensure that you are running the correct (latest) releases of the following three files: wsreg.dll, zen32app.dll and wmgrppol.dll. Your problems should be over thereafter. Have fun, Zen

Folks, The answer is as follows: 1: Ensure that the policies are set up and are located in the correct parts of your NDS tree. Note that the policy serach order is CRITICAL to the success of this. 2: Ensure that you workstation manager is set to trust policies from the correct tree (i.e. not...

Hi, The chances are that you are running nal.exe from your login script. This has an annoying feature of copying the local shortcut to c:\windows\system32 to the start up group. If you have anti-virus installed, sometimes it holds up the launching of nalwin32 thus the network copy is started...

You need to contact Novell Support! Do you not have an admin equivalent account that you can use to change the password of admin? Zen

Your best bet is to use sysprep, however, if you haven't been able to work a solution around the issues with sysprep, your next option is to use your policy to assign a new SID. I have deployed XP to a large multi-national here in Australia, and I used SYSPREP to generate the SIDs. No issues...

Are you running NAL? or Nalwin32? If you are running NAL, it will try to update files in c:\windows\system32 using the users credentials. If the end user is not a member of power users or administrators, they will lose out and the system will crash. Your best bet is to snapshot the files...

What OS are you trying to use? What version of the Kernel are you using? I have deployed XP using 3.21.2 and have no issues at all. Also make sure that you have put the Proxyaddress in the settings.txt and have no spaces after or before it and check that all fields that are not applicable have...

Also, U can use the DLU to put the users into the USers group. These dear souls do not have rights to install software unless specifically over-ridden by a policy. Zen