Thanks I'll give this a try today

This thread is like a honey trap, lol. Works really well.

@RojoLoco said in Webroot: embed keycode in installer:

@JaredBusch said in Webroot: embed keycode in installer:

@RojoLoco said in Webroot: embed keycode in installer:

@gjacobse said in Webroot: embed keycode in installer:

@RojoLoco

Re-downloading and NOT changing the name worked. thanks.

I like that they make it easy. You were just thinking too much, gotta watch that 😉

That said, it is also extremely simple to install with a keycode as a parameter.

How/why did you go all south on this I have no idea. These instructions are right there in the portal.

I deployed with a BAT file originally, before I made my standard images. Here is one example.

REM Server Group Install \\server\share\wsasme.exe /silent /key=SA3B-YOUR-KEY1-HERE-EE34 /lockautouninstall=somepassword /exeshowaddremove /group=2928509553360002652 <---group number for custom group in portal.

I just double click the installer file....

I was installing directly into different groups with different settings. No need to move things in the console later.

@thecreativeone91 said:

It seems to happen with most expensive laptops. They just aren't worth it.better to keep desktops for performance and laptops for mobility.

I owe you an I told you so. Ditching the ASUS too and back on my workstation. Ordered a new motherboard and GTX 980. Going to pick up a weaker laptop.

Turns out that even on the highest end gaming laptops money can buy ( that aren't $4,000+ w/ SLI and 3 minutes battery life ) you can't develop for Oculus, which is my next little adventure.

Sidenote: God it's good to be back on a desktop
rap.PNG