VNIC Placement Policy for VMWare

I'm setting up a new UCS system to run ESXi 5.0 and would like to set up the service profile so that the vNICs get placed in a particular order. I've looked at the vNIC/vHBA placement policy and I think that between this and the service profile this is where I want to configure the required placement. What I'm not sure of is how to configure the placement policy for optimal efficiency.
I have a VIC 1280 card in each B230 M2 blade. I have 12 vNICs (6 on Fabric A and 6 on Fabric B) that I'm creating for the various networks (Prod, DMZ, Management, vMotion, etc...) on each server. When I look at my current vNIC placement on one of the ESXi hosts where I let the system place the vNICs it looks like they are all on vCon1.
Shouldn't my vNICs be split across the vCons? If so how should I split them? Any best practices or suggestions on how I should configure my placement?
Thanks.

This question has been answered pretty heavily here on CSC and on other blogs - so I wont go into great detail.
In short:
vCon's refer to Adapters. One adapter (1280) = 1 vCon.
PCI ordering is managed within the vCon by vNIC/vHBA placement Policy.
Regards,
Robert

Similar Messages

C460 Rack Server with two VIC 1225 - UCSM vNIC placement policy

I am trying to integrate C460 having 2 VIC 1225 cards with UCSM. The objective is to have 2 ethernet interfaces assigned to each VIC , one per FI.
vNIC 1 on VIC 1 - FI A failover to FI B
vNIC 2 on VIC 1 - FI B failover to FI A
vNIC 3 on VIC 2 - FI A failover to FI B
vNIC 4 on VIC 2 - FI B failover to FI A
I have created a service profile with 4 vNICs and assigned to C460. When the UCSM is configured to use the system default for vNIC/vHBA placement policy, all 4 vNICs are assigned to one VIC. When trying to place them manually with 2 on vCon1 and 2 on vCon2, I am seeing insufficient resource error. Both the VIC are recognized and UCSM server tab shows both of them as adapters.
Could someone please let me know how to achieve it?
Thanks!

The C460 has an integrated BCM 57711 which would also be recognized by the system. What's most likely happening is that the VIC 1225s are on vCon1 and vCon3 and the BCM card is on vCon2, since FF is not supported on the Broadcom adapter this would cause the association to fail. Try placing the manual placement with vCon1 and vCon3 and see if this clears up the issue.
Steve McQuerry
UCS - Technical Marketing

Cisco WAAS-Global policy for VMware Vsphere and/or 3par replication

So, this is somewhat annoying that VMware Site Recovery Manager 5.0 does not seem to get much replication acceleration, mostly it is just Pass Through. I have read a couple of Cisco marketing powerpoints that say WAAS will accelerate VMware. But there are no Policies to that effect or configuration assistance. So, vmware has a hundred or so connections in passthrough, all using port 44046, this web site here:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1009562
Shows that this is the port used for Ongoing replication, and port 31031 is used for the initial replication. So, I have two 674-8gb with inline cards. One in main office, one at DR office, both running 5.0.1. The Lan ports on each side point to the LAN and the WAN interfaces on each end point to each other. I have a layer 2 - 90Mbps link between the two locations, so "show cdp neighbor" shows the WAN interface connected.
My question is, is there a policy I should create for this data to be accelerated and stop being "PT Asymmetric"?
Second question, very similar to the first, 3par replication. Same as above, but 3par uses port 5785 and the traffic shows up as "PT In Progress", there are only 6 or so connections in this state, but all are on this port 5785.
If I pull up the pretty graphs on the CM for this device, it shows a well distributed graph, but if I click the check box for "include Pass-Through" it turns all blue and says 100% of traffic is "other-traffic" Since 99% of what goes between these two WAAS devices is VMware site recovery manager 5.0 and 3par replication, I would really like to find a fix for this.

ANSWER ******* SOLUTION ******* ANSWER
I created 2 - Optimization Policy Rules for "WAAS-GLOBAL"
par3-rcopy, destination ports - 5785, 3491-3492, Application - Replication, TFO with DRE Adaptive and LZ
VMware-Replication, destination ports - 44046, 31031, Application - Replication, TFO with DRE Adaptive and LZ
Then I rebooted both WAAS devices and shut off the link for 20 minutes. When I brought the link back online. 100% of data was accelerated, and 99% of the data was classified as "Replication" data. I now get between 60% and 90% acceleration on this "Replication" traffic. The final 1% is other data, remote desktop, ssl, citrix, sql, web...
Lessons learned: The 3par and VMware keep TCP connections open forever, and once the traffic in that session is classified as something, "other traffic" or "Pass Through" it does not change until you reset the connection. So, if you make any changes, you have to shutdown the link, and clear all TCP connections from the WAAS devices, then it will go to a different optimization rule.
Final thoughts: I am not completely sure that the Optimization policy rule "TFO with DRE Adaptive and LZ" is the BEST possible rule to use for this traffic. If anyone has a better configuration for this traffic, I would really appreciate your input.

UCS vNIC Adapter Policy for Linux/Windows question

I am using Citrix XenServer for a hypervisor. I have 4 main vNIC assigned in the server profile. vNIC 0 is what I use for the hypervisor NIC, and the policy I set on this vNIC in the UCS is a Linux profile. But I am noticing that the vNIC's that I am using the Windows VM's are also set to use Linux Adapter settings. What is the typical setup for vNIC's when it comes to the VM's that your assigning ? Should the OS of VM's being used be a factor or is this just dependent on the hypervisor OS that your using ?

Hello,
UCSM comes with default adapter policy with tested settings to meet different OS requirements.
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.1/b_UCSM_GUI_Configuration_Guide_2_1_chapter_010101.html#d95479e943a1635
Is Xen presenting the vNIC directly to your virtual machine ?
Can you please share a specific virtual nic setting for Windows that should be different than vNIC configuration ?
Padma

VNIC failover policy for vMotion network

Hi everyone,
I'm wondering what the recommended design/configuration is for a VMware vMotion network on UCS-B Series v2.0?
1. Create a single vNIC with A-B failover for the vSwitch
2. Create 2 vNICs with A-B failover and make them both active for the vSwitch
3. Create 2 vNICs, 1 with on A and 1 on B both with no failover, and make them both active for the vSwitch
4. Create 2 vNICs, 1 with on A and 1 on B both with no failover, and make 1 active and 1 standby for the vSwitch
The intension is to avoid the vMotion traffic from leaving the FIs, either from within a chassis or across chassis.
Which of the above, if any, would satisfy that?
What are some folks experiences and/or best practices in the real world?
Thanks in advance for any responses.
-Brian

Hello Brian,
Avoid with fabric failover (A-B ) with ESXi teaming and choose option #4
old discussion on this topic
https://supportforums.cisco.com/thread/2061189
Padma

Behavior of UCSM vNIC/vHBA placement policy

hi,
Can anyone please explain me the behavior of UCSM vNIC/vHBA placement policy, and its three options assigned-only, Exclude-Dynamic and Exclude-Unassigned. I have gone through the documentation, but I am not very clear yet.
May be an explaining with an example will help.
Sample scenario.
Full blade having Palo on left side, and Menlo Emulex on right side, with 8 VNICs (4 dynamic, and 4 manual), with each of the three options.
thanks
Tejo

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Tejo, there are two reasons that you would want to use a placement policy.
Full width blades with 2 mezzanine cards - When you have 2 mezzanine cards a placement policy allows you to specify which mezzanine card to assign a vNIC/vHBA to. By doing this you can better load balance the network and storage traffic. In a placement policy the 2 mezzanine cards are identified as vCon1 and vCon2.
Dynamic vNIC Connection Policy – When you have a Dynamic vNIC Connection Policy as part of a Service Profile you want to have a placement policy so that the dynamic vNICs are created below the standard vNIC/vHBAs in the PCI order. Dynamic vNIC connection policies are used in the configuration of VN-Link in hardware. This type of policy requires the Palo mezzanine card though.
Other than those two reasons I don't know when you would use a placement policy unless you just wanted to make sure the OS sees the vNICs/vHBAs on specific PCI slots.
The exclude-dynamic comes into play with the Dyamic vNIC Connection Policies I mentioned in option 2 above. Exclude-unassigned would be where you have some that you want to assign (vNICs) but you don not care about where the vHBAs get assigned.
I personally have only had the need to use them in the 2 scenarios above.
With your specific scenario you would use the placement policy to assign some vNICs/vHBAs to the Emulex card (2 max for vNIC and vHBAs) and some to the Palo (dynamic vNIC connection policy or more than 2 vNICs. Or you might want all of your vHBAs to use the Emulex and all of your vNICs to use the Palo.

Problem with vhba and dynamic vnic placement

Hello all,
I have a problem with vnic/vhba placement policies on an UCS-B:
When a configure a Service Profile, evrything is good:
- I use a "specify manualy" vnic/vhba placement policy and can create this configuration:
- vhba 0 : Order 1
- vhba 1 : Order 2
- veth0 : Order 3
- veth1 : Order 4
- veth 2: Order 5
- veth 3: Order 6
- 8 Dynamic vnic : Order 7 to 14
As soon as i associate this SP with a B200M2 (with palo), UCS manager change this order like that:
- veth0 : Order 1
- veth1 : Order 2
- veth 2: Order 3
- veth 3: Order 4
- 8 Dynamic vnic : Order 5 to 12
- vhba 0 : Order 13
- vhba 1 : Order 14
I've tried several placement policies (auto, exclude dynamique from vcon 1, ....) but it's still the same.
I need to maintain previous order with first vhba, then vnic and finaly dynamic vnic...
My config:
- 1* UCS 5108
- 4 *UCS B200M2 with palo adapter
- UCS MANAGER 2.0(1q)
Does someone know this problem and how to solve it ?
Thanks in advance
Regards
Sebastien.

Sebastien,
When using dynamic vNICs you can't define more than one physical NIC (eth0 and eth1). If you try to create more than two vNICs (using a single VIC) with a Dynamic vNIC policy, it should error out on you during association.
The vCon connection policy is really only used for full width blades with dual mezz cards populated. This gives you some control as to which mezz card and interface vNIC/vHBAs are placed on.
With a B200, the only virtual PCI slots you'll have will be 1 and 2. To my understanding you need the vHBA's as the lowest PCI device # - is that correct?
For your placement policy, set slot 1 to be "Assigned Only", and leave the rest set as "All". Next assign your vHBAs both to Slot 1, and click ok. Associate the Service Profile to the blade and report the results.
This should set the desired placement and ordering for your vHBAs as the lowest.
Regards,
Robert

Dynamic vnic connection policy

I am trying to build a service profile for vmfex but I keep getting a config error
I only have 2 vnics assigned to this blade and I have a dynamic vnic connection policy applied. how many dynamic vnics should i be using? does this depened on how many vms I have on the host? normally is it a one to one mapping for each vm to each dynamic vnic?
also when I apply the profile I get this error

Thanks for the response Jeremy.... Makes perfect sense, I had been told that you could not mix VMFEX with standard VMware switches (I did doubt this as I have used this mixture with none UCS + 1000v configs in the past)...
A few questions if you don’t mind:
1. In your config are you using fabric failover with the vmnics? – If so could you use 1 vmnic with each vswitch (suppressing the error from ESX re mgmt redundancy)
2. Would vmnics4/5 be added to the VMFEX DVS once the DVS has been configured and sent down to vCentre?
3. Are you applying QoS to the VMFEX Port-Profiles for standard VM networking?
4. I have read (somewhere!) that the uplinks on the VMFEX DVS are cosmetic and are not actually used to forward traffic, but more to keep vcentre happy... Not sure if this is true, however, it would also make sense. If this is the case then in the VMFEX world QoS on the uplink vmnics would have no affect and hence applying QoS to the VMFEX Port-Profiles for VM networking??? – Can you clarify this for me?
## Please note, the reason I am looking to use VMFEX is to allow the use of PVLANs on a common backup LAN ###
Lastly, I enjoyed the UCS TrainSignal stuff, very good indeed...
Regards

Fault handling policy for a process in the fault-binding.xml

Can I specify a fault handling policy for a specific process using fault handling framework 10.1.3.3?
<process faultPolicy="DefaultPolicy"/>
I cannot specify the name of the process according to the xsd :(
Can this be achieved?
I have a two different partner links in different processes having the same name. If I add the partner link to the fault-binding.xml what would be the result?
Note: I cannot use bpel.xml to specify the fault policies as of now.

The fault policy bindings file does not allow you to specify a specific fault policy for an individual processes. You can only do this for all BPEL processes (eg: process Level) or at finer grained levels such as partner link levels.
You might be able to use the partner link level for any services that call the process in which you wnat to error handle (eg: Process C needs to be error handled. Process A and B call C so for the partner link names for invoking C could have the fault policy defined for them). Therefore any faults returned from C could propagate back to process A / B and be handled within by the policy outside of Process C. Obviously if this apporach was used you would not want to use process level definitions as C would continue to use this.
If the partner links were of the same name, they should both be handled by the fault policy that is defined withiin the Fault policy (e.g Partner Link level definitions)
An approach that can be used is to specify the fault policy within the bpel.xml file. The information would be added as follows:
</partnerLinkBindings>

<faultPolicyBindings>
<process faultPolicy="AProcessFaultPolicy"/>
<partnerLink faultPolicy="APartnerLinnkPolicy">
<name>insertSSN_dbAdapter</name>
<name>Another_Adapter</name>
</partnerLink>
</faultPolicyBindings>

</BPELProcess>
</BPELSuitcase>
However, I noted you said you were unable to do this. I wasn't sure if this was for technical/governamce reasons or knowledge reasons (unsure where to place to the details.
Hope that helps and does not confuse matters
Dave

80072EE2 - Retrieving Policy for this computer - fails

after several attempts my boot image works fine and starts the pre-TASKSEQ, i enter a password and then i get....
Retrieveing policy for this computer ..... after approximately 2-3 minutes... I get a 80072EE2 error FAILED TO get POLICY.
As this looks like a general issue i went back tru the video guide form The Deployment Team video archive and checked all i did.
Confirmed i followed their procedure to the letter but still the issue happens... can anyone shed some light on this or point me to an article and the correct log file to look at... cheers
SCCM R2 2007- windows 2008R2 domain, SQL 2008R2 DB, etc..
SITE MODE MIXED
ALL roles except DB are on same server.
vmware vCenter Server is sharing this server and it is using http80/https433.
I have the default IIS site using 9080 and 9443 and told config mgr to use these ports.

<![LOG[LOGGING: Finalize process ID set to 772]LOG]!><time="13:59:57.750+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="776" file="tslogging.cpp:1489">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="13:59:57.766+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="776" file="bootshell.cpp:963">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="13:59:57.766+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="776" file="util.cpp:869">
<![LOG[Debug shell is enabled]LOG]!><time="13:59:57.766+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="776" file="bootshell.cpp:974">
<![LOG[Waiting for PNP initialization...]LOG]!><time="13:59:57.813+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:59">
<![LOG[Booted from network (PXE)]LOG]!><time="13:59:57.813+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="configpath.cpp:198">
<![LOG[Found config path X:\sms\data\]LOG]!><time="13:59:57.813+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:553">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="13:59:57.813+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:564">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="13:59:57.813+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="14:00:11.697+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:850">
<![LOG[Starting DNS client service.]LOG]!><time="14:00:11.697+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:597">
<![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="14:00:12.212+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="14:00:12.212+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:850">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="14:00:12.227+000" date="08-13-2010" component="TSMBootstrap" context="" type="1" thread="836" file="tsmbootstrap.cpp:1039">
<![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="14:00:12.227+000" date="08-13-2010" component="TSMBootstrap" context="" type="0" thread="836" file="tsmbootstrap.cpp:1040">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="14:00:12.227+000" date="08-13-2010" component="TSMBootstrap" context="" type="1" thread="836" file="util.cpp:869">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="14:00:12.227+000" date="08-13-2010" component="TSMBootstrap" context="" type="1" thread="836" file="resourceutils.cpp:152">
<![LOG[PXE Boot with Root = X:\]LOG]!><time="14:00:12.243+000" date="08-13-2010" component="TSMBootstrap" context="" type="1" thread="836" file="tsmbootstrap.cpp:921">
<![LOG[Executing from PXE in WinPE]LOG]!><time="14:00:12.243+000" date="08-13-2010" component="TSMBootstrap" context="" type="0" thread="836" file="tsmbootstrap.cpp:936">
<![LOG[Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll]LOG]!><time="14:00:12.243+000" date="08-13-2010" component="TSMBootstrap" context="" type="0" thread="836" file="tsmbootstraputil.cpp:1319">
<![LOG[TsPxe.dll loaded]LOG]!><time="14:00:12.243+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmbootstraputil.cpp:1329">
<![LOG[Device has PXE booted]LOG]!><time="14:00:12.243+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tspxe.cpp:122">
<![LOG[Variable Path: \SMSTemp\2010.08.13.13.58.58.0004.{36B0A0AA-4A8B-497D-80CD-B0CE812C271F}.boot.var]LOG]!><time="14:00:12.243+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tspxe.cpp:134">
<![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="14:00:12.258+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="fwopen.cpp:123">
<![LOG[Executing: X:\sms\bin\x64\smstftp.exe -i 10.216.124.104 get \SMSTemp\2010.08.13.13.58.58.0004.{36B0A0AA-4A8B-497D-80CD-B0CE812C271F}.boot.var X:\sms\data\variables.dat]LOG]!><time="14:00:12.258+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tspxe.cpp:177">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="14:00:12.352+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="commandline.cpp:229">
<![LOG[Set command line: "X:\sms\bin\x64\smstftp.exe" -i 10.216.124.104 get \SMSTemp\2010.08.13.13.58.58.0004.{36B0A0AA-4A8B-497D-80CD-B0CE812C271F}.boot.var X:\sms\data\variables.dat]LOG]!><time="14:00:12.352+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 10.216.124.104 get \SMSTemp\2010.08.13.13.58.58.0004.{36B0A0AA-4A8B-497D-80CD-B0CE812C271F}.boot.var X:\sms\data\variables.dat]LOG]!><time="14:00:12.352+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="commandline.cpp:805">
<![LOG[Process completed with exit code 0]LOG]!><time="14:00:12.414+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="commandline.cpp:1102">
<![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="14:00:12.414+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="fwopen.cpp:146">
<![LOG[Successfully downloaded pxe variable file.]LOG]!><time="14:00:12.414+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tspxe.cpp:187">
<![LOG[we are booted using PXE]LOG]!><time="14:00:12.414+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsmediawizardcontrol.cpp:2242">
<![LOG[we are booted using PXE and we don't use a password or the password is provided by the user]LOG]!><time="14:00:12.414+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsmediawizardcontrol.cpp:2258">
<![LOG[Found network adapter "Intel(R) 82567LM Gigabit Network Connection" with IP Address 10.216.124.52.]LOG]!><time="14:00:12.414+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmbootstraputil.cpp:434">
<![LOG[Run PXE Interactive]LOG]!><time="14:00:12.414+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediawizardcontrol.cpp:2392">
<![LOG[Running Wizard in Interactive mode]LOG]!><time="14:00:12.414+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsmediawizardcontrol.cpp:2394">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="14:00:12.430+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsremovablemedia.cpp:321">
<![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\smscrypt\windes.cpp,185)]LOG]!><time="14:00:12.430+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="windes.cpp:185">
<![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, wcslen(pszPassword)*sizeof(WCHAR), encryptedBuffer.getBuffer(), encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\tscore\tsremovablemedia.cpp,386)]LOG]!><time="14:00:12.430+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsremovablemedia.cpp:386">
<![LOG[Activating Welcome Page.]LOG]!><time="14:00:12.430+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediawelcomepage.cpp:123">
<![LOG[Loading bitmap]LOG]!><time="14:00:12.430+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsmbootstrap.cpp:1150">
<![LOG[WelcomePage::OnWizardNext()]LOG]!><time="14:00:17.609+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediawelcomepage.cpp:314">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="14:00:17.609+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsremovablemedia.cpp:321">
<![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\smscrypt\windes.cpp,185)]LOG]!><time="14:00:17.609+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="windes.cpp:185">
<![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, wcslen(pszPassword)*sizeof(WCHAR), encryptedBuffer.getBuffer(), encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\tscore\tsremovablemedia.cpp,386)]LOG]!><time="14:00:17.609+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsremovablemedia.cpp:386">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="14:00:17.609+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsremovablemedia.cpp:321">
<![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\smscrypt\windes.cpp,185)]LOG]!><time="14:00:17.625+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="windes.cpp:185">
<![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, wcslen(pszPassword)*sizeof(WCHAR), encryptedBuffer.getBuffer(), encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\tscore\tsremovablemedia.cpp,386)]LOG]!><time="14:00:17.625+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsremovablemedia.cpp:386">
<![LOG[Verifying media password.]LOG]!><time="14:00:17.625+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsmediawizardcontrol.cpp:268">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="14:00:17.625+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsremovablemedia.cpp:321">
<![LOG[Spawned thread 324 to download policy.]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsmediawelcomepage.cpp:370">
<![LOG[Entering TSMediaWizardControl::GetPolicy.]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="tsmediawizardcontrol.cpp:483">
<![LOG[Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="environmentscope.cpp:250">
<![LOG[Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="environmentscope.cpp:250">
<![LOG[Setting LogMaxSize to 1000000]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:511">
<![LOG[Setting LogMaxHistory to 1]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:512">
<![LOG[Setting LogLevel to 0]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:513">
<![LOG[Setting LogEnabled to 1]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:514">
<![LOG[Setting LogDebug to 1]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:515">
<![LOG[Loading variables from the Task Sequencing Removable Media.]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:535">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="14:00:17.640+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsremovablemedia.cpp:321">
<![LOG[Setting _SMSMediaGuid TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSBootMediaPackageID TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSHTTPPort TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSHTTPSPort TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSIISSSLState TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSLaunchMode TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSMP TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSMPCerts TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSMPPort TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSMediaPFX TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSPublicRootKey TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSSiteCode TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSUseFirstCert TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSx64UnknownMachineGUID TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[Setting _SMSTSx86UnknownMachineGUID TS environment variable]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:552">
<![LOG[MP Public Certs=308201E63082014FA00302010202105319DA698A5AF7B54D5CC9F1466B9335300D06092A864886F70D01010505003024311430120603550403130B4945445542415050303031310C300A06035504031303534D533020170D3130303731393133323533385A180F32313130303632363133323533385A3024311430120603550403130B4945445542415050303031310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100E3A527AB547C46341D3BA2E78BE5194D8A1CB4ED10D9BD9A1F029E9583323867C72A91260869C0524A4F15521E1F927F513CB21A969508482F9AED66F36508702CB146CC922493A8A3DD82D310A2E7DE72788C5588C0F2A9E5CA98118EDC37E86E6EB384B0D04072749313BDB31A123323AD650F6608236B0BA44B0BF5AF9C270203010001A317301530130603551D25040C300A06082B06010401823765300D06092A864886F70D010105050003818100249AE4CA963BFA261505747FFB59AB9A8DBA4587B4B8B946423992AE87F3FF3100FADFFC58B565FA64A6D833183A165EBE5075F598A0E083C4EEC571827AE6CE3DA82F98BADC03AB13631A738B68C5C40CF1B8D00D48B1A11B221A9C0F396B29DBB22B252ADB9758D43169F7A5154179971485F06B182B3DECFC779A22DBCB04]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:565">
<![LOG[MP: server=IEDUBAPP001.RUV.IE, http=9080, https=9443, default=9080]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:572">
<![LOG[Root CA Public Certs=]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:577">
<![LOG[Missing root CA environment variable from variables file]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:583">
<![LOG[Custom hook from X:\\TSConfig.INI is ]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:616">
<![LOG[No custom hook found]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:453">
<![LOG[No Need to create Authenticator Info]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:742">
<![LOG[Getting MP time information]LOG]!><time="14:00:17.656+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="tsmediawizardcontrol.cpp:753">
<![LOG[Requesting client identity]LOG]!><time="14:00:17.687+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:4910">
<![LOG[Formatted header:]LOG]!><time="14:00:17.687+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:1500">
<![LOG[<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>d1a9b8a3-4dd8-4330-9357-7f2b322325fd</SourceID><SourceHost/><TargetAddress>mp:[http]MP_ClientIDManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-08-13T22:00:17Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="306"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_ClientIDManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
]LOG]!><time="14:00:17.687+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:1501">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: IEDUBAPP001.RUV.IE:9080 CCM_POST /ccm_system/request]LOG]!><time="14:00:17.703+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:7446">
<![LOG[Error. Received 0x80072ee2 from WinHttpSendRequest.]LOG]!><time="14:00:38.747+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:7665">
<![LOG[connect (sock, (struct sockaddr *) &SockAddrIn, sizeof (struct sockaddr_in)) == 0, HRESULT=8007274c (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,657)]LOG]!><time="14:00:59.776+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:657">
<![LOG[socket 'connect' failed; 8007274c]LOG]!><time="14:00:59.776+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:657">
<![LOG[hr, HRESULT=80072ee2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)]LOG]!><time="14:00:59.776+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:7714">
<![LOG[sending with winhttp failed; 80072ee2]LOG]!><time="14:00:59.776+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:7714">
<![LOG[Will retry in 6 second(s)]LOG]!><time="14:00:59.776+000" date="08-13-2010" component="TSPxe" context="" type="2" thread="324" file="libsmsmessaging.cpp:1937">
<![LOG[Retrying...]LOG]!><time="14:01:05.860+000" date="08-13-2010" component="TSPxe" context="" type="2" thread="324" file="libsmsmessaging.cpp:1941">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: IEDUBAPP001.RUV.IE:9080 CCM_POST /ccm_system/request]LOG]!><time="14:01:05.860+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:7446">
<![LOG[Error. Received 0x80072ee2 from WinHttpSendRequest.]LOG]!><time="14:01:26.889+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:7665">
<![LOG[connect (sock, (struct sockaddr *) &SockAddrIn, sizeof (struct sockaddr_in)) == 0, HRESULT=8007274c (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,657)]LOG]!><time="14:01:47.933+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:657">
<![LOG[socket 'connect' failed; 8007274c]LOG]!><time="14:01:47.933+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:657">
<![LOG[hr, HRESULT=80072ee2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)]LOG]!><time="14:01:47.933+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:7714">
<![LOG[sending with winhttp failed; 80072ee2]LOG]!><time="14:01:47.933+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:7714">
<![LOG[Will retry in 11 second(s)]LOG]!><time="14:01:47.933+000" date="08-13-2010" component="TSPxe" context="" type="2" thread="324" file="libsmsmessaging.cpp:1937">
<![LOG[Retrying...]LOG]!><time="14:01:59.493+000" date="08-13-2010" component="TSPxe" context="" type="2" thread="324" file="libsmsmessaging.cpp:1941">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: IEDUBAPP001.RUV.IE:9080 CCM_POST /ccm_system/request]LOG]!><time="14:01:59.493+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:7446">
<![LOG[Error. Received 0x80072ee2 from WinHttpSendRequest.]LOG]!><time="14:02:20.522+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:7665">
<![LOG[connect (sock, (struct sockaddr *) &SockAddrIn, sizeof (struct sockaddr_in)) == 0, HRESULT=8007274c (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,657)]LOG]!><time="14:02:41.551+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:657">
<![LOG[socket 'connect' failed; 8007274c]LOG]!><time="14:02:41.551+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:657">
<![LOG[hr, HRESULT=80072ee2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)]LOG]!><time="14:02:41.551+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:7714">
<![LOG[sending with winhttp failed; 80072ee2]LOG]!><time="14:02:41.551+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:7714">
<![LOG[Will retry in 23 second(s)]LOG]!><time="14:02:41.551+000" date="08-13-2010" component="TSPxe" context="" type="2" thread="324" file="libsmsmessaging.cpp:1937">
<![LOG[Retrying...]LOG]!><time="14:03:04.795+000" date="08-13-2010" component="TSPxe" context="" type="2" thread="324" file="libsmsmessaging.cpp:1941">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: IEDUBAPP001.RUV.IE:9080 CCM_POST /ccm_system/request]LOG]!><time="14:03:04.795+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:7446">
<![LOG[Error. Received 0x80072ee2 from WinHttpSendRequest.]LOG]!><time="14:03:25.823+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="324" file="libsmsmessaging.cpp:7665">
<![LOG[connect (sock, (struct sockaddr *) &SockAddrIn, sizeof (struct sockaddr_in)) == 0, HRESULT=8007274c (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,657)]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:657">
<![LOG[socket 'connect' failed; 8007274c]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:657">
<![LOG[hr, HRESULT=80072ee2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:7714">
<![LOG[sending with winhttp failed; 80072ee2]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:7714">
<![LOG[End of retries]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="2" thread="324" file="libsmsmessaging.cpp:1925">
<![LOG[Send (pReply, nReplySize), HRESULT=80072ee2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2052)]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:2052">
<![LOG[failed to send the request]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:2052">
<![LOG[DoRequest (sReply, true), HRESULT=80072ee2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,5010)]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="libsmsmessaging.cpp:5010">
<![LOG[Failed to get client identity (80072ee2)]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="libsmsmessaging.cpp:5269">
<![LOG[ClientIdentity.RequestClientIdentity (), HRESULT=80072ee2 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,815)]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="tsmediawizardcontrol.cpp:815">
<![LOG[failed to request for client]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="3" thread="324" file="tsmediawizardcontrol.cpp:815">
<![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="tsmediawizardcontrol.cpp:1108">
<![LOG[pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=80072ee2 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,280)]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="324" file="tsmediawelcomepage.cpp:280">
<![LOG[Setting wizard error: An error occurred while retrieving policy for this computer (0x80072EE2). For more information, please contact your system administrator or helpdesk operator.]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediawizardcontrol.cpp:1233">
<![LOG[WelcomePage::OnWizardNext()]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediawelcomepage.cpp:314">
<![LOG[Skipping Confirmation Page.]LOG]!><time="14:03:46.852+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediaconfirmationpage.cpp:169">
<![LOG[Skipping Task Sequence Selection Page.]LOG]!><time="14:03:46.868+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediataskselectionpage.cpp:118">
<![LOG[Skipping Variables Selection Page.]LOG]!><time="14:03:46.868+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediavariablesselectionpage.cpp:155">
<![LOG[Skipping Resolve Progress Page.]LOG]!><time="14:03:46.868+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediaresolveprogresspage.cpp:96">
<![LOG[Activating Finish Page.]LOG]!><time="14:03:46.868+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediafinishpage.cpp:106">
<![LOG[Initializing the countdown timer.]LOG]!><time="14:03:46.868+000" date="08-13-2010" component="TSPxe" context="" type="0" thread="836" file="tsmediafinishpage.cpp:193">
<![LOG[Loading bitmap]LOG]!><time="14:03:46.868+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsmbootstrap.cpp:1150">
<![LOG[Exiting task sequence wizard.]LOG]!><time="14:04:01.064+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsmediawizardcontrol.cpp:2005">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="14:04:01.064+000" date="08-13-2010" component="TSPxe" context="" type="1" thread="836" file="tsmbootstrap.cpp:1118">
<![LOG[Execution complete.]LOG]!><time="14:04:01.080+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:624">
<![LOG[Finalizing logging from process 772]LOG]!><time="14:04:01.080+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="14:04:01.080+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1578">
<![LOG[Successfully finalized logs to C:\SMSTSLog]LOG]!><time="14:04:01.454+000" date="08-13-2010" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1635">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="14:04:01.454+000" date="08-13-2010" component="TSBootShell" context="" type="0" thread="784" file="tslogging.cpp:578">

Probook 640 bios - Enable Intel VT-x and disable trusted execution for VMWare

With the Probook 640, can someone please explain, step by step, how I would make the proper settings in the bios for VMWare virtualization? I need to enable Intel VT-x and disable trusted execution.Thank you.

randallto wrote:
There was another setting in bois I found that required scrolling in the bios screen. Tricky to find with no mouse.
I am not sure if some day these terminologies can be standardized so someone can follow very specific instructions rather than vague instructions that are further obfuscated with the use of technical acronyms.
That is the problem, that error message in VM is not explicit enough as to what steps to take to correct the problem. These bois screen authors decide arbitrarily to name settings as it relates to their world personally and there are not standards.
I still don't know how that got changed in the first place but that is not an issue with VM ware as to what else is changing the setting.
Do you have any explicit suggestions as to how the error message can be improved?

How do I reset GateKeeper policy for one app?

Hi, My system policy is set to 'Mac App store and identified developers'. I used right-click/Open to run an app. How do I reset the policy for that one app so that it won't open if I double-click on it?
Is there a place that lists all the apps that I've overridden the policy for?
Regards, Patrick

Back up all data.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Select the text on the line below by dragging across it. Don't include the blank space at the end of the line.
sudo spctl --disable
Copy the selected text to the Clipboard (command-C). Click anywhere in the Terminal window, then paste (command-V). Press the space bar.
Now switch to the Finder and and select the application in question. Drag it into the Terminal window. More text will be added to what you entered.
Click in the Terminal window to activate it, then press return.
You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command.
You can then quit Terminal.

How to create a group policy for a group not to logout from rdp

there is already a global policy for all users in OU which will disconnect a rdp session after 15 min of inactivity and log user out in another 15 min, (logout 30minutes)
how do I create another policy for a group in that OU so that group user will not be logged out ( executives are asking for this)?

Hi,
In addition to Martin’s suggestions, we can also choose to change the scope of the existing GPO with Security Filtering.
Regarding Security Filtering, the following article can be referred to for more information.
Security filtering using GPMC
http://technet.microsoft.com/en-us/library/cc781988(v=WS.10).aspx
Filter Using Security Groups
http://technet.microsoft.com/en-us/library/cc752992.aspx
Best regards,
Frank Shen

Microsoft Intune was unable to set the desired mobile device policy for one or more users due to the following error: A2CE0100

Hi!
We have fatal or critical error message on Microsoft Intune Portal but all agents are working just fine. Before opening support ticket we would like to hear comments from the experts on this forum. We would also like to fix this error before starting to
manage mobile devices with Intune.
Error message on Intune Portal:
"Microsoft Intune was unable to set the desired mobile device policy for one or more users due to the following error: A2CE0100"
Repeated: 19 times.
Class: (System) Policy
Random Fatal error message on C:\Program Files\Microsoft\OnlineManagement\Logs\PolicyAgent.log found from one Windows 8.1 client:
2015-02-21 08:49:20:704 2852 1ab0 FATAL: DocumentProvider::IndicateToConsumer/pp->ProcessPolicies(NULL, NULL, NULL, NULL) failed with error 0x800704d5.
That said, we are not facing any specific problem but we would like to find symptom of this repeating error message on Intune Portal . We would appreciate to get any thoughts about this case.
Br.
Jukka

Hi Jukka,
Mobile policy doesn't apply to clients using the Full Client download. Please open a support case so the team can assist in further troubleshooting.
Thanks,
Jon L. - MSFT - This posting is provided "AS IS" with no warranties and confers no rights.

Different Password Policy for Different User Groups in ACS 4.2

Hi All,
Can some one provide a solution for the below requirement?
We do have ACS 4.2 appliance managing firewalls of different clients. The users are common i.e, helpdesk administrators. One of the client came up with setting different password policy for managing their devices i.e, the client wants to have min 15 characters as password length. We do have currently 8 characters as min password length. Can we change the password policy to min 15 characters only for managing the firewalls of this client whereas for all other client firewalls we feel better to have 8 characters as min password length?
It seems that these password policies are global & affects all the users.
This is something like, having two sets of password (for each user) policy depending on the client which he is going to manage.
For my knowledge, i think that this is not possible. But, thought to cross-check with experts!
-Jags.

Hi jags,
Yor're correct. Password policy on ACS will affect all internal user. We can't create different password policies for diferent clients/connections/set_of_users
Password validation options apply only to user passwords that are stored in the ACS internal database. They do not apply to passwords in user records in external user databases; nor do they apply to enable or admin passwords for Cisco IOS network devices.
HTH
Regards,
JK

VNIC Placement Policy for VMWare

Similar Messages

Maybe you are looking for