Aller au contenu principal

Not getting prompted for credentials for Image Creation

Thread needs solution

I am trying to capture a master image and went I boot into Acronis I first see "Network Settings" but it doesn't show "server" below. If I proceed I can't see the Network share where I would store the image. In the past I could then fill in the full path and then be prompted for network credentials to connect. I am no longer getting prompted.

I have checked the permissions for the share and they are wide open. Not sure why I am not getting prompted. I need to save this image asap and I'm pulling my hair out. I even restarted the imaging vm server in case that helped. No luck.

Any tips would be appreciated.

0 Users found this helpful

Here is more information. Just tried doing the same process from a laptop and it works exactly like inteded. I get prompted for my credentials if I put in the path to the network share.

I am working with the 1666 build.

Now the machine I am trying to image is BRAND NEW. Lenovo M900Z manufactured in 10/2016. If I try to put in the file path I get the following error:

"You do not have enough privileges to create file "\\server\share name".

I will also add if I try to just get to the Snap Deploy Agent the following error "No internet Connections" rather than IP. But like I said I have a good connection to our network, and when I switch the cable over to the laptop it works great.

Is the NIC driver for this new machine maybe not in the new build?

Is there a way to determine the NIC on the system?  We could pass that to Acronis to have them verify if the driver is present or not.

As for network deployment (without stand-a-lone deployment), I see 2 quick options.

1) Grab a USB 3.0 to ethernet adapter from amazon for $15-$20.  I keep them on hand precisely for this issue since new hardware will always outpace software updates from 3rd party vendors

2) Create a WinPE.wim with the drivers for your NIC and upload the boot.wim to yoru deployment server and use that for the deployment.  It's slower, but should do the trick.

And something else to try...

Have you verified if the new machine is PXE booting in UEFI or Legacy Mode?  Makes sure you're trying UEFI PXE boot since this is such a new machine and is probably defaulting to it.  I don't know anything about this pariticular Lenovo so is hard to say, but I know you can get it to detect the NIC with the right winpe build and drivers injected - unfortunately, you won't be able to use standalone deployment with WinPE so that's the biggest downside... but, you can do this with command prompt commands so it's still there.. Never done it myself, but it's possible if you must do a stand-a-lone deployment.

https://forum.acronis.com/forum/127600#comment-399938

 

Hi Bobbo,

The NIC is showing as Intel(R) Ethernet Connection(2) I219-LM.

I don't have a USB 3.0 adapter on hand but I do have a USB 2.0 adapter. Would that suffice?

USB 2.0 should work as well - just slower (they're limited to 100Mb vs 1Gb in most cases).

SD1666 should support that NIC though.  Have you tried booting the offline Linux recovery media on the system to see if it has a network address just from booting off of that?  Try the UEFI boot first from the rescue media and if that doesn't work, then try the legacy boot with the media and test as well.

If the system is grabbing an IP from the media in one method, or another, but not from PXE booting to the server, you may want to go back to the server, remove the PXE components, reboot, reinstall the PXE components, reboot again (just in case).  

Also check and see if your laptop/desktop system bios has options for UEFI PXE and Legacy PXE as well.  If there is UEFI PXE, use that one, but ensure that UEFI PXE is enabled on the deployment server too. Then go back and try legacy pxe boot.  

So uninstalling and reinstalling the PXE components on the pxe server seemed to do the trick. THANK YOU!!!!!!

Awesome! You're welcome.