AutoCad 2016 Network installation preparing trouble

[YavuzSultanSelim]

Hello,

Tell me, please is it normal if I see this picture since one hour:

Overall progress 1/32 and stuck, but few seconds later I catch a difference:

In red frame you can read (translated from polish) "Creation in progError".

Workstation is Windows 7 x64 with all patches, destination network share has full control for everyone right. The same is under Windows 10 workstation.

Please help...

[YavuzSultanSelim]

Hello,

Tell me, please is it normal if I see this picture since one hour:

Overall progress 1/32 and stuck, but few seconds later I catch a difference:

In red frame you can read (translated from polish) "Creation in progError".

Workstation is Windows 7 x64 with all patches, destination network share has full control for everyone right. The same is under Windows 10 workstation.

Please help...

[emily.xu]

Hello

Welcome to Autodesk Community!

First of all, you can try to install .net 4.5 manually from the folder : \3rdParty\NET\45\wcu\dotNetFramework\dotnetfx45_full_x86_x64.exe, after install .net 4.5 successfully, then retry to install autocad.

Second, check if you have .net 4.6 was installed, if yes, refer to this solution to resolve the problem.

______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[emily.xu]

Hello

Welcome to Autodesk Community!

First of all, you can try to install .net 4.5 manually from the folder : \3rdParty\NET\45\wcu\dotNetFramework\dotnetfx45_full_x86_x64.exe, after install .net 4.5 successfully, then retry to install autocad.

Second, check if you have .net 4.6 was installed, if yes, refer to this solution to resolve the problem.

______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[YavuzSultanSelim]

Thanks for your reply.

At screenshots above you can see preparing of network installation package while transfered to file server, not end user installation.

[YavuzSultanSelim]

Thanks for your reply.

At screenshots above you can see preparing of network installation package while transfered to file server, not end user installation.

[emily.xu]

Do you mean it's during the deployment process? What's your OS?

[emily.xu]

Do you mean it's during the deployment process? What's your OS?

[YavuzSultanSelim]

Yes.

As I wrote above, deployment workstation is Windows 10 Pro, or Windows 7 Pro (polish both of them), both are up to date. Dedstination server is Windows Server 2003 R2.

[YavuzSultanSelim]

Yes.

As I wrote above, deployment workstation is Windows 10 Pro, or Windows 7 Pro (polish both of them), both are up to date. Dedstination server is Windows Server 2003 R2.

[emily.xu]

Try to create a new shared folder on the server with short UNC path, like \\servername\shared folder. and assign full control for Everyone user.

Here is the Best Practices for Creating a Deployment  for your reference.

______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[emily.xu]

Try to create a new shared folder on the server with short UNC path, like \\servername\shared folder. and assign full control for Everyone user.

Here is the Best Practices for Creating a Deployment  for your reference.

______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[YavuzSultanSelim]

Full Control right is alredy applied. I can't use netbios name instead FQDN. Shared folder name is really short - only 3 chars.

When install program stuck, I try to cancel it, but only way to close it is to kill by Task Manager.

[YavuzSultanSelim]

Full Control right is alredy applied. I can't use netbios name instead FQDN. Shared folder name is really short - only 3 chars.

When install program stuck, I try to cancel it, but only way to close it is to kill by Task Manager.

[YavuzSultanSelim]

I try to deploy previous version - Civil 3D 2015, and I get the same: Setup stuck after deploying .NET 4.5, about 28MB is transferred to server.

[YavuzSultanSelim]

I try to deploy previous version - Civil 3D 2015, and I get the same: Setup stuck after deploying .NET 4.5, about 28MB is transferred to server.

[YavuzSultanSelim]

Do you think to open acces for write, take ownership, etc. for 2000+ users is good solution for IT security?...

[YavuzSultanSelim]

Do you think to open acces for write, take ownership, etc. for 2000+ users is good solution for IT security?...

[YavuzSultanSelim · Accepted solution]

Ughhhh!...

Thanks for everybody trying to resolve my problem, but... there is no problem:

Installation stuck because of IDS alert (thanks Checkpoint!  ) and packet rejected from Hyper-V source workstation (thanks Microsoft! )

Any network transmission between H-V Windows Vista, 7, 8 and 10 and deploying serwer (Windows Server 2003) generates a lot of TCP checksum errors. Interesting, but transmission to Windows Server 2008 goes well.

Never mind.

Thanks again.

Y.

[YavuzSultanSelim · Accepted solution]

Ughhhh!...

Thanks for everybody trying to resolve my problem, but... there is no problem:

Installation stuck because of IDS alert (thanks Checkpoint!  ) and packet rejected from Hyper-V source workstation (thanks Microsoft! )

Any network transmission between H-V Windows Vista, 7, 8 and 10 and deploying serwer (Windows Server 2003) generates a lot of TCP checksum errors. Interesting, but transmission to Windows Server 2008 goes well.

Never mind.

Thanks again.

Y.