Home

Results 1 to 6 of 6

Thread: ZCM appliance in a Windows environment.

Threaded View

  1. #1
    Join Date
    Feb 2008
    Posts
    92

    ZCM appliance in a Windows environment.

    Hi all,

    I've set up a Windows server 2012 in a virtual network. This server hosts AD, DNS and DHCP. To test deployment of wim images I addad a ZCM 11.2 appliance to the network.

    When PXE booting a Windows 8 workstation I the ZCM imaging kernel is not being deployed to the machine. Sending Queries to 192.168.10.3 (=ZCM appliance)

    What could be wrong?

    Configuration:
    WinServer2012 ip 192.168.10.2
    ZCM Appliance ip 192.168.10.3

    Firewall on WinServer2012 and ZCM applicance = off

    WinServer 2012 DHCP scope options:
    DHCP Client Scope 192.168.10.100 - 192.168.10.200
    060 disabled
    003 Router 192.168.10.2
    006 DNS Server 192.168.10.2
    066 Boot Server HostName 192.168.10.3
    067 Bootfilename nvlnbp.sys

    WinServer2012 DNS
    WinServer2012 = 192.168.10.2
    ZCMAppliance = 192.168.10.3


    ZCMAppliance:

    /etc/opt/novell/novell-proxydhcp.conf
    #novell-proxydhcp.conf
    #
    #This file contains the required parameters for the Novell ProxyDHCP
    #server
    #
    #Each line that begins with the '#' character is a comment and is ignored
    #by the ProxyDHCP server.
    #
    #Values that are not specified in this file, or that are commented out
    #receive a default value.
    #
    #The Novell ProxyDHCP server is compliant with the following RFCs:
    # RFC 2131 -- Dynamic Host Configuration Protocol
    # RFC 2132 -- DHCP Options and BOOTP Vendor Extensions
    #
    #It is also compliant with the following industry spec:
    # Preboot Execution Environment (PXE) Specification v2.1, published by Intel

    #The value of LocalDHCPFlag indicates whether the DHCP service for this subnet
    #resides on the same server. The Proxy DHCP service needs to behave slightly
    #differently if it is loaded on the same server as the DHCP service.
    #
    #If you load the Proxy DHCP service on the same server as the DHCP service, you will
    #need to configure DHCP vendor-class-identifier (option 60) as 'PXEClient.' For
    #complete information on how to do this, refer to the ZENworks documentation or
    #your DHCP service's documentation.
    #
    #LocalDHCPFlag = 1 --> DHCP service running on same server
    #LocalDHCPFlag = 0 --> DHCP service NOT running on same server
    LocalDHCPFlag = 0

    #LocalInterface indicates the IP address to be used by the Proxy DHCP server. This
    #setting is intended only for use on servers with multiple LAN interfaces. The address
    #must be valid on the server.
    #LocalInterface = 10.0.0.1

    #NovellPolicyEngine is the IP address of the server where a Novell Preboot policy engine is
    #running. Most often, this is a ZENworks imaging service.
    #
    #If no value is specified, then the Proxy DHCP assumes that the service is running on the
    #same server.
    #NovellPolicyEngine = 10.0.0.1

    #NBPx86 is the name of the boot file this service will suggest for all x86 computers.
    NBPx86 = nvlnbp.sys

    #MenuTimeout is the number of seconds the F8 mnenu will be displayed before
    #automatically choosing the first option (always this server and its default NBP
    MenuTimeout = 2

    #The value assigend to ProxyLogLevel determines which events are
    #entered into the system log. Specifying a high level in an active
    #system can quickly fill the log.
    #
    #Valid values: 0, 1, 2, 3
    #
    #Each message from the ProxyDHCP server is assigned a priority level. If
    #ProxyLogLevel is set to a value equal to or greater than a message's
    #priority level, then that message will be entered in the system log.
    #All other messages will be ignored.
    #
    #Depending on the configuration of /etc/syslog.conf, your messages are
    #probably going into /var/log/messages
    #
    #Priority meaning:
    # 1: CRITICAL -- Only service start, stop, and error events are
    # entered.
    # 2: NORMAL -- All criticial information plus notifications
    # of successfully completed client requests are entered.
    # 3: DEBUG -- Includes all information from levels 1 and 2
    # as well as information useful in troubleshooting problems.
    # 4: COMPLETE -- Not intended for use during normal operations.
    # Can quickly fill the log and may impact system performance.
    #ProxyLogLevel = 2
    ProxyLogLevel = 4

    #The ProxyLogFile is the file where all log file entries are placed.
    #ProxyLogFile = /var/opt/novell/log/novell-proxydhcp.log
    ProxyLogFile = /var/opt/novell/log/novell-proxydhcp.log

    #The size of the ProxyLogFile is controlled by the value of ProxyLogFileSize.
    #When the log file exceeds ProxyLogFileSize, it is deleted and restarted.
    #
    #ProxyLogFileSize is assumed to be in megabytes.
    ProxyLogFileSize = 15
    /etc/opt/novell/novell-tftp.conf
    #novell-tftp.conf
    #
    #This file contains the required parameters for the Novell TFTP server
    #
    #Each line that begins with the '#' character is a comment and is ignored
    #by the TFTP server.
    #
    #Values that are not specified in this file, or that are commented out
    #receive a default value.
    #
    #The Novell TFTP server is compliant with the following RFCs:
    # RFC 1350 -- THE TFTP PROTOCOL (REVISION2)
    # RFC 2347 -- TFTP Option Extension
    # RFC 2348 -- TFTP Blocksize Option
    # RFC 2349 -- TFTP Timeout Interval and Transfer Size Options
    # RFC 1123 -- Requirements for Internet Hosts -- Application
    # and Support (Unconditionally compliant with
    # section 4.2 -- TRIVIAL FILE TRANSFER PROTOCOL)

    #TFTPInterface is the IP address that will be used for all TFTP
    #communications. If a value is not given here, the service will try to
    #detect one.
    #
    #This value is most useful for multi-homed servers.
    #TFTPInterface = 10.0.0.1

    #The TransferBlockSize value determines the size of the data block
    #used by the TFTP server to transmit/receive data from a client.
    #
    #For ethernet networks, this value should be 1428.
    #
    #For token ring networks, this value can be 4428, but only if you
    #are sure there are no ethernet segments, otherwise stick with 1428
    #
    #Note that older TFTP clients may be restriced to 512 bytes, the
    #original transfer block size before the adoption of RFC 2348. The
    #Novell TFTP server is compatible with these clients.
    #Valid values: 512 - 4428
    #TransferBlockSize = 1428

    #The TimeoutInterval is the amount of time (in seconds) that the
    #TFTP server will wait for a client to acknowledge before resending a
    #packet. However, since the TFTP server uses an adaptive algorithm to
    #calculate the actual timeout interval, this value is only used as an
    #initial value. It may increase or decrease depending on the
    #performance of the network.
    #
    #This value is only a default. It may be changed at the request of
    #a client. See RFC 2349.
    #
    #Valid values: 1 - 60
    #TimeoutInterval = 1

    #The TFTPDirectory is the directory where the TFTP server can store
    #and retrieve files. All paths submitted to the TFTP server by
    #clients will be assumed to be relative to this directory.
    #
    #Because TFTP has no security, it is suggested that you not place
    #files with sensitive information in this directory, and that you
    #place a space quota on it.
    #
    #The TFTP server will not load if this directory does not exist
    #Linux -- TFTPDirectory = /srv/tftp

    #The TFTPAllowWrites variable tells the TFTP server whether or not to
    #allow users to place new files on the server. Setting this variable to
    #'0' make the TFTP server more secure.
    TFTPAllowWrites = 0

    #The TFTPAllowOverwrites variable tells the TFTP server whether or not to
    #allow users to overwrite existing files on the server. Setting this
    #variable to '0' make the TFTP server more secure. This setting has no
    #effect when TFTPAllowWrites is set to '0.'
    TFTPAllowOverwrites = 0

    #The value assigend to TFTPLogPrioroty determines which events are
    #entered into the log. Specifying a high level in an active
    #system can quickly fill the log.
    #
    #Valid values: 1, 2, 3, 4
    #
    #Each message from the TFTP server is assigned a priority level. If
    #TFTPLogPriority is set to a value equal to or greater than a message's
    #priority level, then that message will be entered in the system log.
    #All other messages will be ignored.
    #
    #Priority meaning:
    # 1: CRITICAL -- Only service start, stop, and error events are
    # entered.
    # 2: NORMAL -- All criticial information plus notifications
    # of successfully completed client requests are entered.
    # 3: DEBUG -- Includes all information from levels 1 and 2
    # as well as information useful in troubleshooting problems.
    # 4: COMPLETE -- Not intended for use during normal operations.
    # Can quickly fill the log and may impact system performance.
    #TFTPLogLevel = 2
    TFTPLogLevel = 4

    #The TFTPLogFile is the file where all log file entries are placed.
    #TFTPLogFile = /var/opt/novell/log/novell-tftp.log
    TFTPLogFile = /var/opt/novell/log/novell-tftp.log

    #The size of the TFTPLogFile is controlled by the value of TFTPLogFileSize.
    #When the log file exceeds TFTPLogFileSize, it is deleted and restarted.
    #
    #TFTPLogFileSize is assumed to be in megabytes.
    #TFTPLogFileSize = 15
    TFTPLogFileSize = 15
    /srv/tftp/boot/settings.txt
    # ZENworks Imaging Settings
    #
    # This file controls the initialization of the ZENworks Imaging Environment.
    #
    # You may edit this file manually or use the ZENworks Imaging Media Creator
    # utility (zmediacreator.exe).
    #
    # For a more detailed explanation of these settings, please see the documentation
    # at Novell Doc: ZENworks 11 Doc - Table of Contents
    #
    # The character starting this line denotes a comment. Any line beginning
    # with that character is ignored when initializing the Imaging Environment.

    # PROMPT should be set to YES if you want to be given a Linux prompt after
    # initialization is complete.
    #PROMPT=YES

    # MANUALREBOOT should be set to YES if you want to reboot manually.
    #MANUALREBOOT=YES

    # PARTITIONSIZE is the size (in megabytes) of the ZENworks Imaging partition
    # that will be created when installing the ZENworks Imaging Engine.
    PARTITIONSIZE=150

    #netdevice can be used to select a specific network adapter
    #netdevice=eth0

    # Use this setting in a DHCP environment.
    netsetup=dhcp,now,all

    #Use the following settings in a static IP address environment.
    #hostip=0.0.0.0
    #netmask=255.255.255.0
    #gateway=0.0.0.0

    #Specify the DNS nameserver
    #Each nameserver should be separated by blank comma
    #nameserver=
    nameserver=192.168.10.2

    #Specify the DNS domain suffixes.
    #Each domain suffix should be separated by blank comma
    #domain=""
    domain=WiKaTest.local

    #Use this setting in case of static network
    #netsetup=-dhcp,now,all

    #PROXYADDR is the IP address or DNS name of the ZENworks Imaging Server.
    #PROXYADDR=
    PROXYADDR=192.168.10.3

    #Use IMGCMD to alter the behavior of automated imaging. If this variable is defined
    #as a script (or a series of commands), then that script (or those commands) will be
    #executed instead of the usual 'img auto' command (see /bin/imaging.s).
    #export IMGCMD="hwtest.s"
    Last edited by WWWilco; 16-Oct-2013 at 03:19 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •