Snap Deploy 5 licensing
I'm considering putting Snap Deply 5 into our 2017 budget. For budgeting purposes I am trying to figure out the liscencing.
Lets say I want the ability to create, or deploy an image to any one of our 200 computers anytime. I imagine I would need a liscense for 200 computers at $25 a piece.
But through attrition we retire some machines and replace them with new ones. Lets say we retire 10 of those 200 computers, but we bring in 10 NEW ones in their place. We still have 200 computers NET total. Would we still be covered for 200 liscences or would we need to buy 10 more (210 liscences and kiss the first 10 goodbye basically).
Also anyone here have Volume liscencing and do you know if you can just declare a "site liscence" and say the entire buisness is covered no matter what (drop dead simple , never have to worry about liscence counts etc). Obviously there would be a cost premium for such a thing I guess.
We are just looking for the simplist solution to take an image, or push an image anytime - new pc deployment, or a problem pc, or a potential Windows 7 to Windows 10 migration, across a variety of Dell Optiplex 390, 3010, 3020, 3040, 5040 (and whatever future Dell model comes out).
Oh I forgot to mention the Dell 5040's have PCIe NVMe Toshiba 256GB SSD drives. That is supported correct?
For your scenario you'll need 200 Full machine licenses (for PC or for Server depending on the operating system in the master image). If the total count of machines doesn't change you'll need to raise a support ticket, so that our engineers can issue new keys for the new machines - this will be free of charge, we only need the confirmation that the old hardware has been dismissed.
Technically no, NVME drives are not supported in the current available public release of ASD5 version 1660. However, 1666beta has been available for a few months now and does have driver support for NVME drives. I don't know why an official version with these drivers hasn't been released yet, but i'm using 1666 beta as are many others in this forum to be able to backup and restore with Snap Deploy and systems using NVME hard drives.
One other note... most systems that come with NVME are being set to RAID mode by the manufacturer by default. On some motherboards that pass on the IRST driver directly to the bios firmware, the default linux media can see these drives just fine. However, OEM systems (like Dell) do not always pass the IRST driver to the firmware so they need to be available in the rescue media. Linux does not have this capabilty so WinPE would be needed instead. ...
OR, change to AHCI mode instead of RAID when you create your images for your single drive NVME systems and there's no issue.
The downside with using WinPE for SD5 is that you lose the ability to peform a stand-a-lone deployment (offline) with the rescue media. I'm not sure why it's not in the winpe, but is in the Linux recovery media. I'm hoping that whatever the next release of SD (not sure when that will be either), will not only have the NVME drivers built in by default, but also allow for stand-a-lone deployment with WinPE.
None of these have been show stoppers, but could be improved upon for sure as NVME drives are much more common place in the latest ultrabooks and performance laptops (and desktops too).
Thanks for the replies.
We are working on the 2017 budget, so hopefully we can get funds set aside for this, but we have all year in 2017 to make the purchase and install. By sometime in 2017 maybe there will be a new version of the product availalbe since there is already a build in beta.
I can tell you on the Optiplex 5040 that has become our new standard build, the M2 NVMe SSD drive (256GB Toshiba) is set to RAID mode out of the bios by default. I can tell you Acronis True Image 2017 WinPE with the Optiplex 5040 drivers injected into it can back up and restore to this machine. I haven't tried a linux boot media from TI 2017.
One more question...
Can the images be written to, and read from a SAMBA share? I haven't had luck in TI 2017 (it just never prompts for authentication after typing in \\ipaddress\sharename like it does for a windows machine).
It would be nice if we can remotely image a machine in a console, like say a machine has a big problem that is surely software. With this product its possible to tell a machine (I suppose there is an agent listening for these types of requests) to reboot into an automatic image deployment where it automatically loads, restarts and joins the domain as the computer name it had before?
Yes, Samba shares should work. We use SD5 offline media for image creation and have them write directly to Windows Server shares and I've tested at home using an SMB share off of my ASUS AC-1900 router too. The benefit for using the Linux media with 1666 is that you get to still use the stand-a-lone deployment option with the Linux recovery media, which is not there in WinPE. WinPE is all-a-round better for driver injection though and was the only way to get certain Intel Nics and NVME drives to detect prior to the 1666 beta release.
With your ATIH media - is that Linux or WinPE as well? With WinPE, you have to mount the share as a drive letter first using net use commands. Once mapped as a drive letter, then you should be able to see it in Acronis. I haven't had any issues with 2017 offline recovery media connecting to SMB shares (my ASUS or a WD MyCloud 4Tb), but others are reporting similar behavior (from Windows though and most that have already mapped the share as a drive letter and then attempting to connect directly via the UNC path in the Acronis GUI). If you're using a public share or the root of the NAS, try making a folder on the root, giving all users access and mapping directly to that folder instead of to the root. Always try to have an account to use though and not a public/open share as Microsoft keeps changing the game on these as they tighten security in Windows 10.
If on a domain, you may also need to to enter the user as domain/username too. On some NAS devices, if not on a domain, you have to enter it such as NASNAME/USERNAME and some even require all caps because it's UNIX based and UNIX can require the exact spelling of the username in many instances (same with terminal commands).