Snap Deploy 5.0.1660 - What did I do wrong?
I want to learn how to use the product with the intention of introducing it into our organization.
I prepared a 2012 R2 server with DHCP and a workstation with W10 (both HP hardware) and on the server I installed the SD5.
I uploaded the Agent and Image Creator to the PXE server.
I made sure the server has a fixed IP and the workstation receives automatically the IP from the DHCP.
Now I can:
1. Boot from the network using F12
2. Start the workstation (in the off state) after creating a deployement task
In both cases I get the Acronis PXE Server menu with Snap Deploy Agent and Master Image creator options.
When I want to run Snap Deploy Agent to load an IMAGE from the served the workstation closes itself.
I want to mnention that I was able to create an image on the workstation using the Master Image Creator that was downloaded from PXE.
Well, what did I do wrong?
Marcel
Moty, you may need to have an open share for PXE boot systems to access the share/files, or supply credentials with username being
domain\username (and make sure that account hasaccess to the share and that the files in the share also have the same access on them as well)
When the system is booted up, it has domain or workgroup information it can pass on through Windows. When booted straight into Acronis through PXE or the stand-a-lone utility, the system has never reached the Windows state and does not possess those credentials at that point. It needs to be supplied somewhere.
See step 6 of this tutorial for supplying the user credentials: https://kb.acronis.com/content/47427
HI Bobbo,
I understand why you think the credentials to access the Master Image are not active but....
1. I Have a server and a workstation (in a workgroup really which can ping each other by IP and the files on the server are fully accesible to the workstation when booted in Windows 10.
2. When I create the template I define the Master Images that are located in a share where "everybody" has full access.
3. I addition I entered the Administrator and password.
4. This is not a user initiated depoyement but a PXE driven deployement.
the moment I press Run - the pxe reboots the workstation and loads the Agent.
The agent on the workstation has not the credentials to access the Image. Nevertheless IT SHOULD have since the workstation is able to let the server know (a log) that the file is not accessible.
I also tried to load the agent by installing the Agent component on the workstation. In thes case the workstation was reported as ONLINE but even inthis case the program shut the workstation down completely.
It seem the server cannot pass over the credentials somehow.
Anu more ideas
thanks abnd regards
Moty
1. I Have a server and a workstation (in a workgroup really which can ping each other by IP and the files on the server are fully accesible to the workstation when booted in Windows 10
That makes sense because in Windows, if the shares have already been mapped, connected or accessed from the workstation to the server, it is already stored in Windows Credential manager and saved. When you PXE boot a system into Acronis, it has no access to the share at that time. I understand you supplied admin credentials in your template, but do those credentials actually work from the Acronis environment since it is not a Windows environment attached to your workgroup?
To be 100%, as a test, I would use the offline bootable stand-a-lone utility and attempt to access the .tib image file from within it. When it asks for credentails connecting to the .tib file share, supply the same account you used, exactly as it was entered in the template, and see if it can connect to the share that way. If it does connect, the mystery deepens a little. If it doesn't you've found the issue. When using the stand-a-lone media or PXE boot into Acronis media on the server, you are basically loading a virtual environment on the local machine, one that is not necessarily already able to connect to your network shares so the proper credentials are key. This is why you need to enter the workgroup/username... in most cases, that will be the servername/username
Until that's verified to work with the offline bootable media, and matches exactly in the template, it's still a guess about having access.
2. When I create the template I define the Master Images that are located in a share where "everybody" has full access.
In Windows, everbody has access when those credentials have already been supplied as severname/username. This does not apply to your PXE booted Acronis system necessarily. You need it to be able to provide those credentials as servername/username too. If you just entered the username in your template, it's not going to work. You can verify this again, using the stand-a-lone bootable media (just to keep it simple). Boot to it and try to connect to your server share where the .tib backup files live. Enter just username and password - it will fail. Enter servername/username and password it should connect.
3. I addition I entered the Administrator and password.
Was that as servername/username or just username? It needs to be servername/username for a workgroup. For a domain it would be domain/username
4. This is not a user initiated depoyement but a PXE driven deployement.
the moment I press Run - the pxe reboots the workstation and loads the Agent
Got it. The Acronis agent is completely seperate from your Windows Workroup. When it attempts to access the share, unless servername/username credentials are supplied, it won't be able to access your Windows server share.
The agent on the workstation has not the credentials to access the Image. Nevertheless IT SHOULD have since the workstation is able to let the server know (a log) that the file is not accessible.
I'm not sure that's true. Both the workstation and server have logging features. Just because the server can detect that something tried to access it, but failed, does not mean the system attempting to access it has the proper credentials. Logging failed connections is stanard practice even in Windows, as well as the Snap Deploy Server.
I also tried to load the agent by installing the Agent component on the workstation. In thes case the workstation was reported as ONLINE but even inthis case the program shut the workstation down completely.
I don't follow what was done here. Don't install any components on the workstation if there is an OS on it already. Did you mean you loaded from the bootable Acronis media? Then connected to the server and started the backup and it just rebooted? That could make sense if there were no proper credentials to access the .tib files on the remote server.
It seem the server cannot pass over the credentials somehow
Technically, the server is never passing over credentials to the workstation. The workstation needs the proper credentials to access the server. This is supplied in the template (servername/username). Or, when using the bootable offline media in stand-a-lone mode, when you map the share and are prompted for credentials and supply servername/username and password for a workgroup server (for a domain server, it would be domain/username and password).
Hi Bobbo,
First I really appreciate your help.
I think we are one step ahead :)
Your last paragraph was -
It seem the server cannot pass over the credentials somehow
Technically, the server is never passing over credentials to the workstation. The workstation needs the proper credentials to access the server. This is supplied in the template (servername/username). Or, when using the bootable offline media in stand-a-lone mode, when you map the share and are prompted for credentials and supply servername/username and password for a workgroup server (for a domain server, it would be domain/username and password).
I understood that whenever the GUI asked for credentials I have to enter "WORKGROUP\Administrator"+ password where WORKGROUP is the "domain name" instead of "Ip...\Administrator" or "<server name>\Administrator".
Using your suggestion I created two bootable CDs: 1. Image creator stand-alone and 2. Agent.
I booted the workstation using first CD and I was able to create a master image and put it on the server.
Using the second CD I was able to restore a master image from the server to the workstation.
Note: I had a problem with the second CD that somehow "cleaned" the drive on the first run. Will check this later.
Now what remains is to send a master image from the server to the workstation when the workstation is OFF and also when the workstation is runinig with the Snap Deploy Agent Installed.
Note: The agent can be remotely installed using the server and It seems Acronis see this option as recommended instead of booting from a CD.
I will report what I will do next.
Note: The main idea behind this problem is the fact that for finding a computer you may use the computer name or the IP while for access rights you must use :
"domain name\user name" or "workgroup name\user name".
What makes it problematic for a user is the input check that is performed by the GUI that lets the use enter "IP\user name" or "computer name\user name" that WILL NOT WORK! I thik the gui accepts also user name and paswword... while isuing an error ifv the user enters user name + wrong password.
Last action for today:
I tried to run a deployment Tast from the server when the workstation was OFF and beeing careful to enter the "domain\user" as needed.
I tried twice: 1 with the normal bootable Agent from the PXE and 2 with a PE boot Image.
IN BOTH CASES I GOT "TIB file is not available".
I am now stuck waiting for somebody at acronis to give me a hint.
Thanks again and regards,
Moty
Hi Moty,
Sounds like you've done things right. The offline bootable backup and recovery has confirmed that the credentials being used to and from your shares is sufficient for read and write access.
Why it's still telling you the TIB is not available in the backup task from the server deployment, though, I'm not sure.
1) Have you tried creating a new Template on the server just to give it a try? I'd create a new one, making doubley sure that the credentials are correct before you ever save it. Also make doubley sure that the path to the .tib is correct too. Are you using IP or computer name - perhaps try one, then the other with the complete UNC path to the .tib.
2) Regarding the location of the .tib files, is the share unique to where the .tibs live? Perhaps the permissions change from the root of the drive to the actual share folder somewhere along the line so it can't traverse through the entire path - wild guess, probably not.
As a test though, what if you create a new folder on the root of the server drive - for instance D:\Tibs. In that root folder, before you put anything in it, set the local file permissions first - make sure that at least "System" and "Administrators" have full file access, and give "users" read access (just in case). Then, create the share and set permissions after that, making sure that whatever account you're using to access the share remotely would have Modify or Full access on the share too (assuming administrators). Then copy your .tib files in there and try to deploy from that location and see if it makes any difference.
3) Have you sent a system report to Acronis yet when you contacted them? Maybe there's something in there that will provide some more help on the problem too.
I tried everythig you suggested but the results are the same: the workstation shuts down with the same "TIB file not available" as before.
FIRST: Thanks a lot for your help.
SECOND: I wil try my luck with Accronis Support.
In the meantime, I had the occasion to go over the user manual and I am well acquainted with all Snap Deploy options...and I am quite not happy with the results.
Best regards,
Mkoty
Hi Bobbo,
Today i tried to check an other assumption: that there is something problematic with w2012R2.
I clean-installed a stand-alone w2008R2 server and tried again.
The result was the same. I did the following:
1.Prepared the PXE
2. Prepared a template
3. Created a deployment task a run it.
The workstation was started by PXE and booted into the Agent.
The Agent contained the server IP and the Worksatation IP (received from DHCP)
The Master Image was definitely accesible the user (domain\user)
The moment I pressed OK on the Agent csreen the workstatioin was shut down.
The error was "TIB not available".
CONCLUSION:
either I did something wrong or someting is missing on the server or there is a bug that "likes me".
BTW I opened aticket with Acronis support.
Moty, did you open the support ticket via email? If so, the response is like 3 days. I would start a chat with them and have them review teh template and your logs to see if they can help pinpoint the issue more quickly. If this was only happening with the default Linux bootable media after PXE, I'd suggest creating a .wim instead, but it seems like you've already tried that?
Couple of other questions - it seems like the computer bios is conifgufed correctly, but I'm wondering if it is trying to launch in the wrong mode too - is your image Legacy/bios or UEFI/GPT? Depending on which it is, make sure that the computer is only set to boot the same way to try and rule out it booting into the wrong mode.
ALSO, when booting pxe, are you booting legacy PXE or UEFI PXE? Try both and see if one works better than the other. I think we always use the legacy pxe, of the image being deployed, but maybe one will work better than the other in your case.
Moty, when you contact support - see if there is a version 1662 you can test as well. Just saw this posted in another forum with HP Elite Books not working with PXE boot either.
Hi Bobbo ,
I did my tests with the newest equipment (HP Zx40) that can boot in UEFI or BIOS.
I tried both - if I disable UEFI it will boot in BIOS... but it did not help.
I order to cancel the possibility of access problem to the shared folder on the server, I did a Image Deploy to the workstation from the same server using Acronis Backup 11.7 CD. It was 100% . Which was similar to doing a restore with a SNAP DEPLOY CD.
The access to the server when the workstaion is booted from UNIX is probably done using SMB protocol. They probably implemented a change that corrupted the transfer of pameters from the server to the client and back to the server (to get access to files).e developers at
BTW - of course I tried with PE (Installed ADKSETUP 10) and created a WIW file that I uploaded to PXE. It behaved exactly the same as the Unix based boot.
What about the 1664 - did those guys at Acronis supply a Release note to the user? I wil see if it is downloadable.
I have an additional question: Do you use Snap Deploy 5 yourself? Are you using NOW 1660?
Maybe the problem I have did not manifest in older revisions.
Regards,
Moty
We're using 1660, but mostly with the stand-a-lone boot media because our base image works fine with everything we throw at it as long as we generalize the hardware and run SID changer during the deployment. We then use the Dell driver.cab packs to quickly install the correct drivers on each system during the deployment process as well and that keeps things simple and efficient (although not fully automated, but pretty darn close). There's really not a lot of advantage to using the server for deployment (in our environment) as we do all of our imaging and deployment locally where physical access is possible.
Unfortunately, we don't have a single HP though either to test with - almost entirely Dell (although we do have some Surface Pro's and various other Windows tablets, but just about everythign else is Dell so it could be specific to the HP's you're using). Do you have any other hardware this is happening on as well? If it can be duplicated across multiple devices, more likely to be an Acronis issue, but if it's on a speciific models only, could be a hardware compatibiltiy issue.
I have not seen that other release mentioned in that other post - hopefully Acronis support engineers can provide it to you if they did for the other person. I'm guessing it was either a custom build with specific drivers for that person or a beta with general driver support and/or bug fixes that may be a future final release at some point.
Has Acronis support gotten back in touch with you at all?
HI,
WE both know that the stand alone version of SnapDeply works... even is in my case was somtimes "cleaning" the target disk.
I have also proved that Acronis Backup can connet easily to my "bank" of images on my server (SMB protocol has no problem in my case).
I assume that if Accronis Backup could change the SID you would practically never have used SnapDeploy :)
My intention was (because of distributed locations and variable types of hardware) to try the various scenarion that Snat Deploy was meant to enable...
Those scenarios are corrupted now.
If you do not need the SID change I think an Acronis Backup Bootable USB is more stable.
Also I know that using a SSD (2TB for example) with all your drivers and images and connecting it to your target machines could be really faster. You can connect the SSD dirctly to the SATA 3 (and power) and get over 200 Mb/s transfer rate. Or you could conncet the SSD via a SATA to USB3 (USD15) connector to an USB3 (powered) port on the target and get 100 Mb/sec transfer rate. Is small and centralized shops the server is sometimes an overkill.
Thanks
Marcel
Hi Marcel,
Did support ever get back in touch with you? Curious if you were able to get 1662 as well - others in this forum are still suggesting they are able to get it directly from support engineers on a case by case basis and they seem to be having the same issues with the current HP Elitebooks as what you're eperiencing with your HP too.
Hi Bobbo,
I am quite disappointed with 1st level at Acronis: they have no specific experience with Snap Deploy and only apply predefined rules ...
Moreover they are not fast enough to diagnose and escalate a problem that can bother many users and potential users.
In this case, I did not get any feedback that may say for example "we tried 1660 on different hardware and the option works".
Then I will believe it depends on hardware (in this case new HP chipsets) and will be willing to test any suggestion they may have to go ahead and solve the problem.
Other possible feedback is for example "we found the option works in build 1556 (or earlier) but not in 1660".
Then I will wait for the next build...
I believe the second option is more probable...
So far no reaction.
Marcel
Hi,
I tried to run the deployrement task from the same test server to a Panasonic Portable 4 years old.
I had a proven Acronis Backup image and the failure was the same.
If you have any connections at Acronis I think you should mention that I tried but I had to give up.
After I opened this discussion I noticed that many customers are trying to use the product bat fail, as can be seen from the various topics.
The complaints are snowballing and no serious replys to support requests or forum questions.
It definitely seems the product is not stable so far.
Regards,
Marcel
Hi Moty,
I will pass it along the MVP chain, and hopefully someone internally can look into this more. I don't know why someone couldn't get you v1662 if that is a beta that seems to be working on the HP Elite's and has been given to others by support engineers and reported to be working. Very disappointed that no one reached out to you to supply this to you. Unfortunately, I don't have access myself and don't have a copy of 1662 either though. Please send a PM to Acronis General Manager, gaidar and I'm sure he will reach back out to you. Be sure to reference this thread about your problems, include your support case # and also reference these posts about beta v1662 as well:
https://forum.acronis.com/forum/117376
https://forum.acronis.com/forum/116296
Hi Bobbo
Today I sent a PM to Acronis General Manager as you suggested.
I hope somebody will now check the problem not theoreticaly but in practice.
So far the low level support was a disappointment.
And nobady was "man enough" to tell me when and if my remote scenario was tested.
Regards,
Marcel
Excellent. I hope you do hear back directly soon. Feel free to send direct PM's to support engineer Ekaterina too if you're getting the run-a-round from the default technial support . She has been very responsive, but usually needs the contact to be initiated from the user as she is only able to check the forums occassionally, but will try to respond quickly to PM's (as available).