Cyberlink PowerDirector 13 Activation Problem

If you’re getting an activation issue after using the KEYGEN, change these registry settings….

Open Run Command. type in “regedit”.

Use the FIND Command = prod_activate

“Prod_Activate=OnlineCheck” to “Prod_Activate=OfflineCheck”

Also, locate ureg.ini in install folder… Edit “Prod_Activate=OnlineCheck” to “Prod_Activate=OfflineCheck”

Esxi on Dell PowerEdge T20

Follow these steps:

1.   ESXI Customized Image from DELL:

VMware ESXi 5.5 Image Driver Details | Dell US

2.   Intel I217LM Nic Card Driver from here:

https://communities.vmware.com/servlet/JiveServlet/download/2278196-112346/net-e1000e-2.3.2.x86_64.vib

3.   ESXi Customizer to overwrite existing driver.

VMware Front Experience: ESXi-Customizer

4.   RUFUS to burn the Modified ISO to USB.

Rufus – Create bootable USB drives the easy way

5.  Make sure the BIOS as the VT -D Setting Enabled (Virtual Machine Setting is CHECKED).

Boot the Machine with the Bootable USB, Press ‘SHIFT+O’ and type noIOMMU press Enter.

It will boot the OS and skip ‘Initializing IOV’ Error.

This should work as

To Enable noIOMMU option every-time the OS boots,

a.  Activate SSH and connect to the ESXi server

b.  type: esxcli system settings kernel set –setting=noIOMMU -v TRUE

that will make it bypass the “Initializing iov” everytime.

VMware ESXi 5.5.0 1331820 Purple Screen / Dell Poweredge 2950

Motherboard nonmaskble interrupt, undiagnosed.

vmx-swga

PCPU 0: USSUVUUU

 

IMG_20150319_123204

 

FIX = Change Virtual NIC in the VM indicated from E1000E to E1000.

 

 

===

‘ \ ,u ll ll‘:–1.», .. |…i1.1 l =’=1:,:.;L| -fill I111 _ > _ V ]_ V”
‘~ r”1\ ‘l>|\\|v|’l I||».1r|1 rn|n|mil-1hl|- i|’\fPr‘l’|’Pt]- “F”1i-7l’l’_’l_”-“*”7- H7‘? ‘mu ha ‘7 h‘3’_’j'”‘arfi p[nh]”H’ P “1 I ‘I
‘ ‘ 1 ‘.‘u||l||\\ :1 -1,‘||-i|l1||mH|1|||_| :u\1m‘1‘-JQLIIJIJ-.1-1IJxZ?l5B
-1’ \l<\\ ‘-CH! “||- ,\’|]~1Il-lin|1|\u’. H xi-‘1
I\’|A H |\‘.‘.|l’-.-‘l||lll
|l\l‘l I-1| I: ll-‘1lillllhiwllllllllll Uflk llpt inn: lI:Li:l]b:l8.?E|5
u. \l “.||| 1’4.|:nll:ll)‘-11:1l1\J|1=-Hm.1,]‘)]P_1||i|;vF’o||in;lnt@v||kc|*m:lRn0ur:|‘+Ux5?5 ‘5-taukl Ux4lZ5UUOQUDDB
ll–1 1.”.lll l‘I|i‘)5-H: llhul lfilllldvihif lri ]l’nn ic_HnSauel3unl»<er’nelI¥noueF+Clx4‘3 Stack: C|x4l25Ul1’3d’3f U
ll-‘1 \.”.I\l 1‘h|’1t-ll: l|1,»<‘1l:H1l]:1n:l38S28]NI‘1IChr:ul»<Lint 1B0tt0n@unkeFn6lfln0uer‘+CIx5U ‘>tacl~<I U><8?8‘3c|l69d38d l
11- 1 |.”.\\l l’M’H‘ll : III‘-vi lfllllldn/‘::‘34|‘ ]BH_Dra inAncIDi€-ab le lnterruptsfiunkernelNnc|uer+C|xF3 stack: lIIx4lUHF|r2[]ba;|
ll–1l.”|l!l l’M.:.ll1:lll\-1l:HlUduE>3u83llDT >Intr‘Handlerfiunkerne1fln0ver*Ux1aF stackl Ox4125U119db58
|l- -1 I .”.l|l l’l<i.\-1|! : I lI\-1 llllllldrcf lllhfl ]qate_entrg[lunkeFnelflncluer ¢Ux64 stack! CI>(1Ub
ll-‘ll.”|lIll’3l1lI‘\H1ll\x‘1lfiU[]::ld32‘3d]PUuEI‘_HGltPCPU@\)HkBI‘l”lEl”I10’J8I‘*0X1r6 stacki OX1]
ll–1 l./”-Ill 1‘MhrH : l llx-1 18l][]eU‘1eBS9 ]CpuSchedIdleL0opIntflumkernelflr|0uer*+Ux4bd stack: Dxef‘
II.–1 l.-“-Ill l‘)1h|)HT llJx4 18DOeO5493D]CpuSchedD ispatchliumkernel¥fnover+EIx1630 stack: Elx325aS
lIv\ l/‘Hill l‘!dd‘)B 1 ([‘lx4 l8UUeD55c6S ]CpuSchedHa itfivmkerne lBnover+l3x24S stacki l3x412SlJ11‘3de38
lI~<‘1l/‘JillP31117383[Dx418DUd6dC54T]HOI‘ldHaitlI’l1;|!vmker‘nCl#rIUUCI‘+U><3a? stack: Uxfl
ll-’11./’5-l|1l‘ldcb8: [l]x41BUl]e3a9BaU]LinuxThread__Futexl3<I‘|c|ne>l$<None>*Ux3BEl Stack! DXBEI
(I141/“.1111 l‘)dl‘DBI[Ux418UDe3?a212]User_LinuxSgscallHandlcr@(H0ne)fl<H0ne)+Ox2l‘2 stack! Gx412501.l9dF28
II1-11;/‘€\lIll‘3df18t [Ux41BDOdea9b4d]User_LinuxSgscallHar|dler[lvml<ernelfln0ver+Elx1d stack: 0x35800580
|l><4l’/‘hlll1‘3dl‘28:[Ux418Dl3def1EI64]gatc_|:nt|-gfiwokerneHtnover+0x64 stack: Dxllilb
lm–at f\.»[]xIJ gs=Dx41BlEl4BDDE|E|Dl3 KgS=DXl3
linrndunp to disk. Slot 1 0|‘ 1.
I inul ized dump header (12/12) l)iskDunp= Successful.
Nu file configured to dump data.
llnhuqger uaiting(uo|-Id 57414) —- no port For remote debugger. “Escape” for local debugger

VMware vCenter Converter P2V to ESXi 5.5 Steps [If Getting Errors using Infrastructure]

IF VMware vCenter Converter Standalone Client VM/Physical or TIB to VMware Infrastructure ESXi Server Fail, try the steps below.

Important: Remember to REMOVE VMWare tools from the VM before doing the below.

  1. Used VMware vCenter Converter.
  2. Migrate to Version Workstation 8.X.
  3. Open in Workstation, add Server running ESXi
  4. Power off the VM
  5. Go to Settings
  6. Open options (tab)
  7. VM Tools
  8. Choose top answer “Update manually (do nothing)”
  9. The drag over to Esxi or use the upload command.
  10. Drag and Drop to Server in VMWare Workstation
  11. Run

Vmware Upload Failed: A specified parameter was not correct

Uninstall VMware tools from the VM…

Then:

1. Power off the VM
2. Settings
3. options (tab)
4. VM Tools
5. Choose top answer “Update manually (do nothing)”
The drag over to Esxi or use the upload command.

Problem solved.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2036689

Symptoms
Cannot import an OVF to vCloud Director (vCD)
Importing an OVF to vCD fails
The virtual machine was created in VMware Workstation
Cannot deploy the OVF in vCenter Server
Cause
VMware Workstation includes a parameter that allows all virtual machines to use the default settings to upgrade VMware Tools.
This setting is not supported in vSphere and vCD environments.
Resolution
To workaround the issue:
Open the the OVF file using a text editor.
Locate the line:

<vmw:Config ovf:required=”false” vmw:key=”tools.toolsUpgradePolicy” vmw:value=”useGlobal”/>

Change this line to:

<vmw:Config ovf:required=”false” vmw:key=”tools.toolsUpgradePolicy” vmw:value=”manual”/>

Save the file.

Note: The .mf file must be deleted after saving the changes.

Alternatively, export the virtual machine back to Workstation and change VMware Tools update option to manual:
Right-click the virtual machine in Workstation and click Edit Settings.
In the Options tab, change the VMware Tools update option from Use application default to Manual.