Provisioning Server 7.6 – Windows 2012 R2 shows “getting device ready” every time the machine boots up .

Getting devices ready is a OS related process wherein all the devices are been enumerated (Moreover we call it a hardware enumeration) .it is actually not an issue but it’s a process that its executed every time the machine boots up .If OS detects a change in the device it enumberates it and install the required driver for that device.

By default its run every time the machine start.

Reference to Microsoft link : http://blogs.technet.com/b/wincat/archive/2012/09/06/device-management-powershell-cmdlets-sample-an-introduction.aspx

( Hardware enumeration is something that the vast majority of Windows users don’t need to worry about. Thanks to an extensive PnP infrastructure, the process of identifying devices, installing drivers and controlling those devices is handled transparently by the Operating System)

Related:

  • No Related Posts

PXE don’t start

I need a solution

Hi all,

I have all tutorials and all videos read and watch but I don’t have a solution for my problem. I have no idea what to do in my case.

I have GSS Suite on a Server 2012R2 in a VM ESXI and on the same VM machina a windows 7 prof. Client. If I want to boot PXE

I become the following screen and after this my Win7 boot normaly but don’t boot PXE. Is there anyone who have the same problem?

Thanks for your help

0

Related:

  • No Related Posts

ipxe -> symantec pxe chain

I need a solution

ipxe -> symantec pxe chain

Hallo all, 

Could someone help us with the following?:

We boot our clients using ipxe, users get a menu to boot from. 
One of the options is symantec.

We chainload using the following command: 
chain tftp://192.168.200.28/BSTrap/x86pc/BStrap.0, this works in BIOS.

For UEFI we use:
chain tftp://192.168.200.28/BTrap/X64/BStrap.efi, this goes wrong.

If i leave out ipxe and directly boot Symantec via pxe in UEFI, it works after setting option 60 PXEClient.

I have already contacted the ipxe developers, they said i need to ask Symantec:

http://forum.ipxe.org/showthread.php?tid=18169

Could someone help me with this i have tried a lot of things but i am not able to resolve it?

Thank you
Wietse

0

Related:

  • No Related Posts

Dell Latitude 5591 bizarre ghost behavior (drive shows as 2 TB but it’s only 256 GB)

I need a solution

Hello,

We received a batch of latitude 5591’s and at first I struggled getting one to boot to PXE / TFTP to pull down the ghost image. Had to change to Legacy boot mode in order to do that. Now, when I boot it pulls down the ghost client fine and runs it. I thought I was going to be fine but then I saw this:

notice the source says “Local drive [1], 244198 MB” but the MB remaining says 2093737 (??)

please help

0

Related:

  • No Related Posts

Can’t boot to PXE

I need a solution

Have 3 site servers running DS. Recently recreated the PXE files and now cannot PXE boot on 2 of them. Get:

File: BootBCD

Status: 0xc000000f

Info: The Boot Configuration Data for your PS is missing or contains errors.

Found this article: https://www.symantec.com/connect/forums/winpe-10-preboot-dont-work which seems to apply that has a link to another article but that link is dead for. It also refers to running a script but have no idea what that is.

The one DS that does work is Windows Server 2012 and the 2 that don’t are Windows server 2008 r2. About 3 months ago I updated to ADK 1803 on the NS. I am very afraid of doing any of this without clear instructions as the one that is working is high volume and I do not want to mess that one up.

Thanks in advance for any support you can provide.

0

Related:

  • No Related Posts

Action Recommended to Secure the Cisco Nexus PowerOn Auto Provisioning Feature

Cisco Nexus devices support an automatic provisioning or zero-touch deployment feature called PowerOn Auto Provisioning (POAP). This feature assists in automating the initial deployment and configuration of Nexus switches. POAP is enabled by default and activates on devices that have no startup configuration or when Perpetual POAP has been configured using the boot poap enable command.

As with other automatic provisioning technologies, such as Cisco Zero-Touch Provisioning or Cisco Smart Install, some basic assumptions are made about the initial deployment environment. First, that administrators know that the feature exists and is enabled by default. Second, that the Layer 2 (L2) network on which a device initially connects is secure.

By design, the POAP feature leverages several unauthenticated protocols to obtain the initial configuration file for a device. When a device with POAP boots and subsequently fails to locate a startup configuration, such as on the first startup after unboxing or after a restoration of factory defaults, the device enters POAP mode. The device will attempt to locate a DHCP server through a connected management interface1. Then the switch will listen for a DHCP response that includes at a minimum the following:

  • An IP address
  • A default gateway
  • Option 66 (TFTP server name) or Option 150 (TFTP server address)
  • Option 67 (boot file name)

If the Nexus device receives multiple DHCP responses that meet these requirements, the first DHCP response received will be accepted, and POAP will move to the next stage of the device configuration. If no DHCP responses that meet these requirements are received prior to the timeout period, the device will exit POAP mode.

If a DHCP response is accepted, the Nexus device will attempt to connect to the provided TFTP server to retrieve the Python or Tool Command Language (Tcl) POAP configuration script specified within the boot file option. The switch will then execute the script to retrieve the specified software and device configuration. The Nexus device software and configuration may be retrieved using Secure Copy Protocol (SCP), FTP, or SFTP. The downloaded Nexus software will be assigned as the active image, with the configuration file scheduled to be applied when the device restarts.

Several steps in the POAP configuration process rely on a secure network segment to obtain critical startup information. While the POAP feature disables itself after a configurationis applied to a device2, it is critical that customers properly secure the networks in which POAP may be utilized. Some customers may want to disable the POAP feature and use other methods to configure a Nexus device out of the box. To this end, Cisco has added multiple new commands to disable POAP that will persist across a reset to factory defaults and the removal of a configuration. For guidelines on securing a POAP environment, as well as information about disabling the feature, see the Details and Recommendations sections.

This advisory is available at the following link:
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190306-info-poap

1On some Nexus chassis-based devices, the DHCP solicitation may also be sent using all front-panel Ethernet interfaces of the installed router processor.

2The POAP feature will not be disabled if Perpetual POAP has been configured using the boot poap enable command and will run on each reload of the device.

Security Impact Rating: Informational

Related:

  • No Related Posts

Can't edit App layer, boot error 0xC000000F; but OS and Platform Layers work OK

First, verify this is not https://support.citrix.com/article/CTX238440 . The error message is normally different, but that’s the most likely cause: language issues.

Second, Add Version to your OS layer, run CMD As Administrator, and do the following. This will trigger a new scan of critical OS system files to update our list of critical system files.

CD Program FilesUnideskUniservice

Uniservice.exe /B

<Reboot>

Then finalize that and test creating a new app layer again.

Otherwise, this is a system driver that has not been properly copied to the boot disk. This does not apply to OS and Platform layers because the boot disk is handled differently. But with App Layers, the boot disk is a thin disk that contains just enough Windows to get minifilter drivers running. 0xC000000F means we missed copying something to the boot disk.

Unfortunately, you can’t tell what we missed. What you need to do is version your OS layer to get a record of a successful boot. Login, run msinfo32, Boot, and enable Boot Logging. This will create a boot log file called C:Windowsntbtlog.txt that conatins, in order, every file loaded during boot. Reboot to generate the log, and copy it to a file share. Leave the packaging machine for the OS layer open, you will need it again in a minute.

On the packaging machine for the App Layer that fails to boot, attach your Windows installer ISO. Boot from that. When you get the the first Windows Setup dialog, type Shift-F10, which will bring up a command prompt window. In this machine, X: is the CD-ROM, C: is the mini boot disk, D: is the OS layer, and E: is the package disk. We care about C: and D:. Specifically, we care about what is in D: that is not in C: but should be.

Load up ntbtlog.txt in Notepad. In the command prompt window, type “C:” to get to the C drive, and then “CD Windowssystem32”. All of your important files will be in Windowssystem32 or windowssystem32drivers. Read through the ntbtlog.txt, and check that each file is on your C: drive. For any files which are not, copy them from the D: drive with a command like this:

XCOPY /CHOK D:Windowssystem32driversntosext.sys C:Windowssystem32drivers

The parameters to XCOPY ensure that the permissions and attributes are copied as well. Note every missing file. Once you have found and copied in the missing files, reboot from the hard drive, not the CD-ROM. Verify that your app layer now boots. Cancel the App Layer.

Back in the OS layer, edit C:Program FilesUnideskUniservicebootfile.txt. Add the correct path for the missing files to the bottom of bootfile.txt. Note that the directory separators are / instead of . So for instance, add the following line:

C:/Windows/system32/drivers/ntosext.sys

C:/Windows/system32/drivers/clipsp.sys

Save the file, finalize, and attempt to create a new app layer with the new OS version. If this works, please open a Support Case and let Citrix know about this file. Normally we would have picked it up with the Uniservice /B scan. We will likely ask for other information from your OS layer, including if you know what updates might have triggered this. However, with the modified bootfile.txt, you should be able to continue your deployment.

Related:

  • No Related Posts

PPG may reject MMSC connections

By default the PPG is configured with the tw_recycle setting enabled:

[root@ppg2 ~]# awk '/# Added by Gemini Mobile/,/recycle/' /etc/sysctl.conf# Added by Gemini Mobile 'factory' framework:##net.ipv4.tcp_tw_recycle = 1

This allows the fast reuse of connections in the TIME-WAIT queue. As an extra check it rejects the connection if a SYN packet arrives with timestamp (TSVal) smaller than the last known timestamp from this peer. This check is additional to the PAWS protection, but it only works if the TSVal values of the packets received from the same IP address are monotonically increasing.

This requirement is not met when the MMSC is behind NAT. The man page is also clear that this causes problems with NAT:

 tcp_tw_recycle (Boolean; default: disabled; since Linux 2.4) Enable fast recycling of TIME_WAIT sockets. Enabling this option is not recommended since this causes problems when working with NAT (Network Address Translation).

Because reuse of connections in the TIME-WAIT state may be needed for a high rate of requests, the tw_reuse option should be set:

 tcp_tw_reuse (Boolean; default: disabled; since Linux 2.4.19/2.6) Allow to reuse TIME_WAIT sockets for new connections when it is safe from protocol viewpoint. It should not be changed without advice/request of technical experts.

Related:

  • No Related Posts