Quantcast
Channel: Ivanti User Community : All Content - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 1803

Provisioning - Preferred Servers configuration best practises

$
0
0

Purpose:

 

This article describes our recommendations regarding Preferred Servers configuration to avoid problems with capture/deploy image within Provisioning task.

 

I. Configure Preferred Server three times: NetBIOS, FQDN, IP

 

In some environments it is hard to determine which value (NetBIOS, FQDN, IP) should be used when configuring Preferred Server to work properly for Provisioning actions: Capture/Deploy Image. To avoid problems, please set up same Preferred Server three times with NetBIOS, FQDN, IP. Configuration should look similar to one below:

 

preferred_server_conf.PNG

 

II. Capture Image - account permissions

 

To successfully capture an image during Provisioning job our process needs to have sufficient permissions to network share on a Preferred server. Provisioning uses the same configuration as the Content replication module. However, it was not designed to switch between Read-only and Write account:

Provisioning process uses account configured as Read-only in Preferred Server configuration to map network drive then to write image file there. Please remember to give "Write" permissions to "read-only" account if Preferred Server is in use for Provisioning tasks.

The warning "The user name and password should provide only READ access to the preferred server" applies mainly to content replication/SWD and does not take Provisioning into account. When imaging from Preferred servers, the account needs to have read and write privileges to the network share.

Related articles:

 

How to configure the Preferred Server (Target) for Content Replication: https://community.ivanti.com/docs/DOC-20782

How to configure a Preferred Package Server: https://community.ivanti.com/docs/DOC-1385


Viewing all articles
Browse latest Browse all 1803

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>