Unfortunatly ePO and AutoUpdate Architect work a bit differently. I found a new version of the AutoUpdate Architect, version 1.1.2, on their site and it resolved the issue. It no longer pulls the "System Compliance Profiler."
Hope the info helps someone... remember: It's not a bug it's a feature!
I am having a similar problem related on HTTP repositories. I noticed the addition of the "System Compliance Profiler Templates" in my master repository. After I do a 'pull' if I manually remove that from my repository I am able to successfully replicate.
I don't know if that helps at all but...
To get the right syntax open a command window and type:
"C:\Program Files\Novell\Zenworks\NALWIN32.EXE" /?
You should get a window that shows the switches you can use with NalWin32. Once you have the proper syntax just incorporate it into the filetype.
The easiest way to edit the word...
Are you running NAL Application Explorer and NAL Aplication Launcher? Just a shot in the dark but Novell has like 1 TID is all that says you can't run them both at the same time. We just recently found the TID ourselves. It causes NAL to do some pretty messed up stuff when they are both running...
We have a simalar setup except we have upgraded to 2003 servers running edir with zen 4. The bigest problem we have run into is the NDS console and the imaging server control for multicast sessions will only show up on the Console, that is to say the screen physically attached to the server...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.