Snap Deploy 3 File name, location or format error
I am using Snap Deploy 3. I created a bootable disc through the management console. Boot to the disk and tell it I want to create a Master Image. Everything is okay with network settings. When I try to select the location on my network I want it to back up to I get the following error:
The file name, location, or format \\fs2\MyBackup.tib is not valid.
Please type the file name or location in the correct format.
Looking through the forums someone suggest in other post that they had similar problems, where they did have sufficent permissions.
Permissions is not a issue. I am an administrator on the network and permissions are set correctly. I have tryed creating a new directory with out any luck.
As far as a name format goes, I went ahead and tryed it with the name Snap Deploy defaults it to. Still no luck.
Any help would be great.
Thanks
I have this same problem, Yana. I have tried every thing you suggested except for turning off digitally sign communications since I have no idea what that is and couldn't find it anywhere. I have the latest version of snap deploy and it just will NOT allow me to use a properly formatted name for the .tib file.
Hello Janelle!
Thank you for finding time to leave a comment and report about the issue, I really appreciate it!
I will be glad to provide you with the instructions on how to find and change Digitally Signed Communications.
The user name should be specified in the form of SERVER\USER or DOMAIN\USER.
If you are trying to access a server in a domain that is controlled by Windows Server 2000/2003 and still cannot log in to a server, please try the following:
- Open Active Directory Users and Computers on the domain controller (Windows Server 2000/2003);
- In the console tree, right-click Domain Controllers, click Properties, and then click the Group Policy tab;
- Click Default Domain Controllers Policy, and then click Edit;
- Open the Computer Configuration \ Windows Settings \ Security Settings \ Local Policies \ Security Options folder.
- Set the following:
Microsoft network server: Digitally Signed Communications(always) to Disabled
Microsoft network server: Digitally Signed Communications(if client agrees) to Disabled
Network Security LAN manager Authentication level to Send NTLMv2 response only\refuse LM & NTLM
You can read Microsoft Knowledge Base Article 823659 regarding this issue as well - it can also be useful.
I would appreciate if you could keep is posted regarding the issue.
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you.
Hello, Yana.
Your suggestion worked; however, I would recommend that no one else tries that last step. Wow! Good thing we are a small department and I am the only IT person. We use logon scripts to map drives and those all began to fail. The authentication used from a logon script must be different. In any case, I backed out that last policy change and all was well so it probably is not necessary, just disabling the digitally signed communications.
thank you
Dear Janelle!
Thank you your comment and for finding time to let us know that the issue got resolved! It's really great to know that currently you're all set and everything is working!
Thank you for mentioning that you faced the issue with the last step. I'm really sorry for the inconvenience caused. Since this information is also available in the KB, I will send this information to our Web team to update the article.
Thank you once again for your cooperation and patience, I really appreciate it.
Should you need anything or have any new questions - don't hesitate to leave a comment, we will definitely help you.
Not sure how Janelle managed it, but I had to also turn back "Send NTLMv2 Response Only" so that it would allow NTLM. Otherwise the login to the share would fail and it would lock my account!
I had to disable "Digitally Sign Communications" as well.
Correction: "Digitally Sign Communications" was fine. That can be set to "Always". But setting "Send NTLMv2 Response Only" made it impossible for the Acronis bootable CD to access network shares.