DeployAnywhere won’t import drivers, says Failed to find any drivers to add.

I need a solution

We had a previous image process and are switching over to the altiris methodology so I am importing all drivers (Windows 10) into the deploy anywhere database.

I am getting a lot of them coming back with “Failed to find any drivers to add”  which then causes it to default to the base windows driver for this device.  One specific device that caused me to really notice this is a synaptics touchpad where when the drivers are the default MS it doesn’t work.  I downloaded the drivers from MS using update driver, then grabbed the drivers out of the driverstore and told it to try and import and again it says nothing found.   I was thinking maybe they weren’t there, so I ran a test with the folder I grabbed using DISM in winPE and sure enough they get installed fine that way.

Any ideas on what I can possibly do to get it to recognize the drivers?

This is the full error

Failed to import driver: \mynsservernscapbinwin32x86deploymenttempdriverssynpd.inf_amd64_a20ab0cba6ba9630synpd.inf [Failed to find any drivers to add.]

0

Related:

  • No Related Posts

AppLayering 4.x – OS layer creation fails with error “An error occurred. The required file ‘OSType.txt’ was not found on your OS disk. Please obtain the application layering OS machine tools, run ‘Setup_x64.exe’ on your OS image”

AppLayering only supports MBR and Hyper-V Generation 1 machines. It does not supports GPT and Generation 2 machines.

Capture ELM logs and in camlogfile we could see, if GPT is being used.

2017-11-17 11:43:46,085 INFO Threadpool worker Shell: EXEC: Device Boot Start End Blocks Id System

2017-11-17 11:43:46,085 INFO Threadpool worker Shell: EXEC: /dev/nbd1279p1 1 4294967295 2147483647+ ee GPT

Note: App Layering will only look at the first partition or two, so if we are running setup64.exe and it’s saving on a 3rd or 4th partition, it’ll never look at that partition by design, so it will never find ostype.txt there.

Related:

  • No Related Posts

Restrict LDAP users on ZENworks Reporting

Ron van Herk

I like using ZENworks Reporting to generate custom reports for ZENworks Configuration Management or for ZENworks Service Desk but there has been one thing I found very annoying, the ability to manage LDAP users and the Roles within ZENworks Reporter. The ZENworks Reporter appliance configuration makes it very easy to add an LDAP source to …

+read more

The post Restrict LDAP users on ZENworks Reporting appeared first on Cool Solutions. Ron van Herk

Related:

  • No Related Posts

How to disable “OK but failing” email notification while ICMP health checks is running for particular ip??

I need a solution

Hello.

Can anyone help me with my problem?

I need to perform ICMP echo checks for one IP address and I want to recive only one email message when host is down. If I deploy policy like that “interval = 30 threshold = 5” and when host is down – I will recive two messages – “OK but failing” and then “failed”. Can I disable intermediate message like “OK but failing” and recive only useful messages like OK or Failed. This intermediate email messages are useless because ICMP echo can get lost in Internet but I will recive useless beeps on my phone.

Thanks for any advice.

0

Related:

  • No Related Posts

Enrolling existing devices to the Apple Device Enrollment Program for simplified provisioning with #ZENworks

jblackett

Introduction As I am sure you are aware, using the Apple Device Enrollment Program (DEP) to enroll devices simplifies the process of provisioning devices with ZENworks and allows you to perform over-the-air supervision of the device. Supervising an iOS device opens a variety of additional settings and profiles that can be applied to restrict the …

+read more

The post Enrolling existing devices to the Apple Device Enrollment Program for simplified provisioning with #ZENworks appeared first on Cool Solutions. jblackett

Related:

  • No Related Posts

Auto Deployment stuck at “Client Record Updated”

I need a solution

I’m not sure where to start, but I’m running a distribute disk image job against a machine.  PC reboots, connects to PXE, boots to WinPE, loads drivers successfully, and establishes a network connection.  Then it starts dagent.  Dagent displays “client record updated” but that is where it stops.  It shows the address for my server, it shows the address for the client, but it doesn’t display computer name or MAC address.

I’d like to troubleshoot why it hangs.  Are there logs I can create that can assist here?  Any advice or tips would be appreciated.  I’m running a trial version of GSS 3.2 trying to get a proof of concept going so we can evaluate this product.  

0

Related:

  • No Related Posts

Re: NDMP-Backup Error >> Failed to propagate handle; TimeOut after inactive

hello COmmunity,

After switching to a new backup server and a platform change from Linux to Windows, we get errors in certain processes when backing up NDMP file systems

suppressed 138 bytes of output.

.144324:nsrndmp_save: Adding attribute *policy workflow name = eNAS-VDM-016

.144324:nsrndmp_save: Adding attribute *policy action name = backup

.06/18/18 07:52:22.821430 NDMP Service Debug: The process id for NDMP service is 0x5a670b0

42909:nsrndmp_save: Performing DAR Backup..

83320:nsrndmp_save: Performing incremental backup, BASE_DATE = 44478769945

42794:nsrndmp_save: Performing backup to Non-NDMP type of device

174908:nsrdsa_save: Saving the backup data in the pool ‘dd3 enas’.

175019:nsrdsa_save: Received the media management binding information on the host ‘bkpmgmnt01.sis.net’.

174910:nsrdsa_save: Connected to the nsrmmd process on the host ‘bkpmgmnt01.sis.net’.

175295:nsrdsa_save: Successfully connected to the Data Domain device.

129292:nsrdsa_save: Successfully established Client direct save session for save-set ID ‘2854701209’ (eNAS1-DM-01:/root_vdm_9/VDM-16_fs2) with Data Domain volume ‘enas_001’.

42658:nsrdsa_save: DSA savetime = 1529301142

85183:nsrndmp_save: DSA is listening for an NDMP data connection on: 10.109.130.100, port = 8912

42952:nsrndmp_save: eNAS1-DM-01:/root_vdm_9/VDM-16_fs2 NDMP save running on ‘bkpmgmnt01.sis.net’

84118:nsrndmp_save: Failed to propagate handle 0000000000000000 to C:Program FilesEMC NetWorkernsrbinnsrndmp_2fh.exe child process: Das Handle ist ungültig. (Win32 error 0x6)

84118:nsrndmp_save: Failed to propagate handle 0000000000000000 to C:Program FilesEMC NetWorkernsrbinnsrndmp_2fh.exe child process: Das Handle ist ungültig. (Win32 error 0x6)

accept connection: accepted a connection

42953:nsrdsa_save: Performing Non-Immediate save

42923:nsrndmp_save: NDMP Service Error: Medium error

42923:nsrndmp_save: NDMP Service Warning: Write failed on archive volume 1

42617:nsrndmp_save: NDMP Service Log: server_archive: emctar vol 1, 93 files, 0 bytes read, 327680 bytes written

42738:nsrndmp_save: Data server halted: Error during the backup.

7136:nsrndmp_save: (interrupted), exiting

— Job Indications —

Termination request was sent to job 576172 as requested; Reason given: Inactive

eNAS1-DM-01:/root_vdm_9/VDM-16_fs2: retried 1 times.

eNAS1-DM-01:/root_vdm_9/VDM-16_fs2 aborted, inactivity timeout has been reached.



Strangely, these messages do not occur on all file systems, but rather randomly.

Does anyone know this error message and knows where the problem lies? The evaluation of the Celerra logs has so far revealed nothing.

Best Regard

Cykes

Related:

  • No Related Posts

NDMP-Backup Error >> Failed to propagate handle; TimeOut after inactive

hello COmmunity,

After switching to a new backup server and a platform change from Linux to Windows, we get errors in certain processes when backing up NDMP file systems

suppressed 138 bytes of output.

.144324:nsrndmp_save: Adding attribute *policy workflow name = eNAS-VDM-016

.144324:nsrndmp_save: Adding attribute *policy action name = backup

.06/18/18 07:52:22.821430 NDMP Service Debug: The process id for NDMP service is 0x5a670b0

42909:nsrndmp_save: Performing DAR Backup..

83320:nsrndmp_save: Performing incremental backup, BASE_DATE = 44478769945

42794:nsrndmp_save: Performing backup to Non-NDMP type of device

174908:nsrdsa_save: Saving the backup data in the pool ‘dd3 enas’.

175019:nsrdsa_save: Received the media management binding information on the host ‘bkpmgmnt01.sis.net’.

174910:nsrdsa_save: Connected to the nsrmmd process on the host ‘bkpmgmnt01.sis.net’.

175295:nsrdsa_save: Successfully connected to the Data Domain device.

129292:nsrdsa_save: Successfully established Client direct save session for save-set ID ‘2854701209’ (eNAS1-DM-01:/root_vdm_9/VDM-16_fs2) with Data Domain volume ‘enas_001’.

42658:nsrdsa_save: DSA savetime = 1529301142

85183:nsrndmp_save: DSA is listening for an NDMP data connection on: 10.109.130.100, port = 8912

42952:nsrndmp_save: eNAS1-DM-01:/root_vdm_9/VDM-16_fs2 NDMP save running on ‘bkpmgmnt01.sis.net’

84118:nsrndmp_save: Failed to propagate handle 0000000000000000 to C:Program FilesEMC NetWorkernsrbinnsrndmp_2fh.exe child process: Das Handle ist ungültig. (Win32 error 0x6)

84118:nsrndmp_save: Failed to propagate handle 0000000000000000 to C:Program FilesEMC NetWorkernsrbinnsrndmp_2fh.exe child process: Das Handle ist ungültig. (Win32 error 0x6)

accept connection: accepted a connection

42953:nsrdsa_save: Performing Non-Immediate save

42923:nsrndmp_save: NDMP Service Error: Medium error

42923:nsrndmp_save: NDMP Service Warning: Write failed on archive volume 1

42617:nsrndmp_save: NDMP Service Log: server_archive: emctar vol 1, 93 files, 0 bytes read, 327680 bytes written

42738:nsrndmp_save: Data server halted: Error during the backup.

7136:nsrndmp_save: (interrupted), exiting

— Job Indications —

Termination request was sent to job 576172 as requested; Reason given: Inactive

eNAS1-DM-01:/root_vdm_9/VDM-16_fs2: retried 1 times.

eNAS1-DM-01:/root_vdm_9/VDM-16_fs2 aborted, inactivity timeout has been reached.



Strangely, these messages do not occur on all file systems, but rather randomly.

Does anyone know this error message and knows where the problem lies? The evaluation of the Celerra logs has so far revealed nothing.

Best Regard

Cykes

Related:

  • No Related Posts