jrhodes1 Respected Contributor.
Respected Contributor.

Re: 2017 U4 imaging not working

We only have one Zenworks server so I cannot see it using another server.

What has happened recently is that we have just replaced/moved our zenworks server from Windows Server 2012 to Windows Server 2016. We mainly did the server replace because we have just moved from our old XenCenter virtual platform (with 8 year old servers that where getting a bit dodgy) to our new VMWare platform which is on our new blade server.

The new 2016 server has the same name and IP address of the old server which I know is no longer running as it is powered down and I disabled its network access so that it could not talk to the network if it accidently got turned on.

When I am PXE booting the test machines it says

ZENworks PreBoot Execution (PXE) Agent: v17.4.0
(C) Copyright 2008- 2019 Micro Focus or one of its affiliates.
Sending Queries to “the correct IP Address”

So as far as I know it should be contacting the correct server.
0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

OK. But for some reason does it not receive tntfs.ko.

Alt-F2 on the imaged machine when you have selected "Manual
Maintenance" shows some info. In fact Alt-F1..F4 do.

Try yanking up the logging level of TFTP on the imaging server and see:
https://support.novell.com/Platform/Publishing/989/3418069_f.1.html

What I have seen a lot is that tntfs.ko never gets replicated to the
correct dir on the imaging server.

- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jrhodes1 Respected Contributor.
Respected Contributor.

Re: 2017 U4 imaging not working

I have tired pressing F2 is there something specific I am looking for? I did see this whilst it was loading into maintenance mode

loading tftp://IP_ADDRESS/efi/x86_64/config -> /download/file_0000
error 68:
loading tftp://IP_ADDRESS/efi/x86_64/root -> /download/file_0001

also I tried gathering the logs it did come up with an error saying it

error: [Error 5] Access is denied: 'C:\\Users\\USERNAME\\AppData\\Local\\Temp\\5/zen-info\\conf\\loader\\AddPatchlinkAnalyzeReporting.xml'

is this normal? However I did get some info from it I think do trying to pick thought it

Thanks for the help
0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

I do not think that that error is anything to be concerned with. Let me yank up logging on my Imaging server and see what it should look like.

On mine, tntfs.ko is in: /srv/tftp/17.2.0/x86_64

Change in file %ZENWORKS_HOME%\conf\preboot\novell-tftp.conf:

TFTPLogLevel = 3 (remove the hash before)
Restart tftp or entire box
(service novell-tftp restart on linux)

look for log in the path indicated in same file:
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25808] [] [zmgtool] [] [Using port 46734 for client 10.0.20.81] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25839] [] [zmgtool] [] [Read request from 10.0.20.81:44703 for 17.2.0/x86_64/tntfs.ko] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:25.000] [25808] [zmgtool] [25839] [] [zmgtool] [] [File sent to 10.0.20.81:44703 --> 17.2.0/x86_64/tntfs.ko] [] [] [] [Imaging]

(/var/opt/novell/log on linux)

Remember to change back afterwards as you will fill up disk quickly with debugb logging

- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jrhodes1 Respected Contributor.
Respected Contributor.

Re: 2017 U4 imaging not working

Right I have done that and there where to following errors in the log

[DEBUG] [04/26/2019 10:16:51.000] [2664] [zmgtool] [8992] [] [zmgtool] [] [ Sending OPTION ACK to 10.0.0.0:2070] [] [] [] [Imaging]
[DEBUG] [04/26/2019 10:16:51.000] [2664] [zmgtool] [8992] [] [zmgtool] [] [Read request from 10.0.0.0:2070 failed:
Error in sending an OPTION ACK packet] [] [] [] [Imaging]

[DEBUG] [04/26/2019 10:18:47.000] [2664] [zmgtool] [6524] [] [zmgtool] [] [File not found :efi\x86_64\config] [] [] [] [Imaging]
[DEBUG] [04/26/2019 10:18:47.000] [2664] [zmgtool] [6524] [] [zmgtool] [] [ Sending ERROR packet to client 10.0.0.0 on port 60395 --> File not found] [] [] [] [Imaging]

[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [10276] [] [zmgtool] [] [File not found :efi\media.1\info.txt] [] [] [] [Imaging]
[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [10276] [] [zmgtool] [] [ Sending ERROR packet to client 10.0.0.0 on port 60398 --> File not found] [] [] [] [Imaging]

[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [2096] [] [zmgtool] [] [File not found :efi\license.tar.gz] [] [] [] [Imaging]
[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [2096] [] [zmgtool] [] [ Sending ERROR packet to client 10.0.0.0 on port 60399 --> File not found] [] [] [] [Imaging]

[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [5276] [] [zmgtool] [] [File not found :efi\part.info] [] [] [] [Imaging]
[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [5276] [] [zmgtool] [] [ Sending ERROR packet to client 10.0.0.0 on port 60400 --> File not found] [] [] [] [Imaging]

[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [9596] [] [zmgtool] [] [File not found :efi\control.xml] [] [] [] [Imaging]
[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [9596] [] [zmgtool] [] [ Sending ERROR packet to client 10.0.0.0 on port 60401 --> File not found] [] [] [] [Imaging]

[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [2644] [] [zmgtool] [] [File not found :efi\autoinst.xml] [] [] [] [Imaging]
[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [2644] [] [zmgtool] [] [ Sending ERROR packet to client 10.0.0.0 on port 60402 --> File not found] [] [] [] [Imaging]

[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [5616] [] [zmgtool] [] [File not found :efi\driverupdate] [] [] [] [Imaging]
[DEBUG] [04/26/2019 10:20:53.000] [2664] [zmgtool] [5616] [] [zmgtool] [] [ Sending ERROR packet to client 10.0.0.0 on port 60403 --> File not found] [] [] [] [Imaging]

i have just given the errors i can provide the whole log if that is needed but it does look like files are missing/not being copyed

Thanks
0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

Jrhodes,
> i have just given the errors i can provide the whole log if that is
> needed but it does look like files are missing/not being copyed


Below is the relevant from mine. You see that it is after efi\driverupdate that it reads the tntfs entries. Compare that to your log.

[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25836] [] [zmgtool] [] [File not found :efi/driverupdate] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25836] [] [zmgtool] [] [ Sending ERROR packet to client 10.0.20.81 on port 57187 --> File not found] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25836] [] [zmgtool] [] [Closing port 57187 used by client 10.0.20.81] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25808] [] [zmgtool] [] [Using port 53813 for client 10.0.20.81] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25838] [] [zmgtool] [] [Read request from 10.0.20.81:55930 for HighPerfDriver.conf] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25838] [] [zmgtool] [] [File sent to 10.0.20.81:55930 --> HighPerfDriver.conf] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25838] [] [zmgtool] [] [Closing port 53813 used by client 10.0.20.81] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25808] [] [zmgtool] [] [Using port 46734 for client 10.0.20.81] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:24.000] [25808] [zmgtool] [25839] [] [zmgtool] [] [Read request from 10.0.20.81:44703 for 17.2.0/x86_64/tntfs.ko] [] [] [] [Imaging]
[DEBUG] [04/26/2019 07:29:25.000] [25808] [zmgtool] [25839] [] [zmgtool] [] [File sent to 10.0.20.81:44703 --> 17.2.0/x86_64/tntfs.ko] [] [] [] [Imaging]
- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

Jrhodes,
> efi\driverupdate


Also verify that the tftp dir on the imaging server has the required
files

The tftp directory contains files such as configuration files and
binaries used by ZENworks to perform imaging tasks. The directory is
located on the Imaging server in /srv/ on Linux and in %ZENWORKS_HOME%
\share\ on Windows.

Especially HighPerfDriver.conf and that it points to the correct file

#
#Wed May 02 20:31:49 EEST 2018
NTFSDriver=17.2.0/x86/tntfs.ko
NTFSDriver_x64=17.2.0/x86_64/tntfs.ko


- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jrhodes1 Respected Contributor.
Respected Contributor.

Re: 2017 U4 imaging not working

Hi I have checked the HighPerfDriver.conf and they seem to be pointing to the correct location

#
#Wed Apr 24 00:31:41 BST 2019
NTFSDriver=17.4.0/x86/tntfs.ko
NTFSDriver_x64=17.4.0/x86_64/tntfs.ko

However in the share\tftp\efi folder all the files above are not there as far as I can tell

Thanks,
0 Likes
jrhodes1 Respected Contributor.
Respected Contributor.

Re: 2017 U4 imaging not working

I meant to ask what is the best way to get these files? Can I just copy the files from somewhere or will I have to do some kind of repair install?

Thanks
0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

I have always had a problem here that the tftp files do not replicate
reliably so I just copy them manually.

So, you have the HighPerfDriver.conf in the tftp dir?

- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jrhodes1 Respected Contributor.
Respected Contributor.

Re: 2017 U4 imaging not working

Yes the HighPerfDriver.conf is in the tftp dir and as far as I can tell it’s content is correct.

#
#Wed Apr 24 00:31:41 BST 2019
NTFSDriver=17.4.0/x86/tntfs.ko
NTFSDriver_x64=17.4.0/x86_64/tntfs.ko

Which is where the files are

However the following files that created errors are not in the tftp\efi dir

efi\media.1\info.txt
efi\license.tar.gz
efi\part.info
efi\control.xml
efi\autoinst.xml
efi\driverupdate

I have checked the backup of the tftp dir I took before moving/replacing the server and they are not in there either.
0 Likes
jrhodes1 Respected Contributor.
Respected Contributor.

Re: 2017 U4 imaging not working

Hi has anyone got any ideas on how we can fix this problem I am getting desperate now we really need imaging back up and running, I have done some checking into the novell-pbserv.log file and found the following error when we try to image a machine.

(LicenseCheck) Checking Imaging License] [] [] [] [Imaging]
(ZENIMGWEB-CSCKT) Call to connect returned value greater than zero. Continuing with SSL port.] [] [] [] [Imaging]
(ZENIMGWEB-CSCKT) g_WebServiceHostName: Discovery.hollingworth.internal.] [] [] [] [Imaging]
(ZENIMGWEB-CSCKT) SSL connection using version: TLSv1.2.] [] [] [] [Imaging]
(RNT) Server GUID is: d853cdff36f188f6af431d14bd804a21] [] [] [] [Imaging]
(RNT) Imaging License Info: 1] [] [] [] [Imaging]
(LC) open**** connection,server address, 0.0.0.0] [] [] [] [Imaging]
(LC) open connection,client address, IP ADDRESS] [] [] [] [Imaging]
(LC) open connection, IP ADDRESS] [] [] [] [Imaging]
(PCV) received PROXY_CMD_VERSION] [] [] [] [Imaging]
(HC) versions: 10, 10, 174000] [] [] [] [Imaging]
(PCV) done PROXY_CMD_VERSION] [] [] [] [Imaging]
(PCGI) received PROXY_CMD_GET_IMAGE] [] [] [] [Imaging]
(PCGI) Image File: D:\Novell\Novell\ZENworks\work\content-repo\images\base54.zmg] [] [] []
Imaging]
(SIF) sending D:\Novell\Novell\ZENworks\work\content-repo\images\base54.zmg] [] [] [] [Imaging]
(SIF) start download] [] [] [] [Imaging]
(CW) send failure, 4440, 0, -1, 0] [] [] [] [Imaging]
(PCGI) done, PROXY_CMD_GET_IMAGE] [] [] [] [Imaging]
(SCEM) send failure, -1, 0] [] [] [] [Imaging]
(ECC) close connection, IP ADDRESS] [] [] [] [Imaging]
(ECC) CS] [] [] [] [Imaging]

Does this give any one any ideas?

I have only just noticed that some reason the diagnostics for our server are saying

Status: server is unreachable
And all processes say Not Available

This was working until recently so I do not what has stopped these from working I don’t know if this has anything to do with the problem or not.

I have been thinking about opening a service request about this but sadly we are a school and our licensing deal does not give us access to service requests, I think we have to pay if we want them, however I am having trouble finding information on how I might be able to purchase them.

Thanks to everyone who has helped me so far it is very much appreciated.
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.