Vmware fusion packaging

[#1]

Good morning,

I have compiled a VMWare Fusion build following the instructions provided by
JAMF and have encountered an inconsistency between my version and the
instructions. I downloaded the installer for VM version 3.1.3 and followed
the JAMF instructions as best as I could. In the Packaging section, the
document describes where I need to place the 'license.txt' file within the
licensePane.bundle package (show package contents, place license.txt in
licensePane.bundle/Contents/Resources/, close) - in version 3.1.3, VMware
has added a 'licenses' folder within /Resources/, and placing 'license.txt'
into the designated location does not work. Putting the license.txt file
into the 'licenses' folder doesn't either.

Has anyone successfully built an enterprise installer with Fusion version
3.1.3? And if so, what is the secret to adding the license?

Thanks
Dave

-- -- -- -- -- -- -- -- -- --
Dave Simon
Director, Media Engineering and Operations

T +1.415.808.3594 | F +1.415.808.3535 | C +1.617.908.5043
600 Harrison St € San Francisco, CA € 94107

PRN | media where & when it matters

[#2]

Thanks for the tip on licensing ­ the before/after snapshot worked well.

Next question: on the deployment of XP, is there a way to provision the
virtual machine with the correct machine name and user accounts within
Windows? For example, my Macbook Pro is 'sfdsimonlt01' and my virtual
machine is 'sfdsimonvm01' with me as a local admin ‹ is there a way to
automate the machine naming and user account provisioning?

Thanks again everyone

Dave

[jarednichols]

I wasn't able to ever to get the license to work in this method. I did a snapshot before and after licensing to make a "license" package that follows the app installation. I tend to not like to bake in license codes anyway in case they change.

j
---
Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

[nessts]

I do the same a simple script that runs the command to add the license at priority 11 and vmware install is priority 10, using the package as it comes from vmware.

in perl…
my $lic_cmd = '/Library/Application Support/VMware Fusion/vmware-vmx';
my @lic_opts = qw(--new-sn);
my $lic = "somelicensekey";
system($lic_cmd, @lic_opts, $lic);

--
Todd Ness
Technology Consultant/Non-Windows Services
Americas Regional Delivery Engineering
HP Enterprise Services

[nessts]

check your mail, I just sent a way to do this 30 minutes ago.

--
Todd Ness
Technology Consultant/Non-Windows Services
Americas Regional Delivery Engineering
HP Enterprise Services

[jarednichols]

I think if you use sysprep you may get some options on the default machine name. I'm not sure there's any way for it to pull the machine name of the host machine as a base for the machine name of the VM. Remember, Windows itself doesn't know it's a VM.

j
---
Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436