I had a Snapin for Eset and was deplying perfectly on previous laptops.
We now have new laptops and the Return code is 5033.

I had a Google on return codes 5033 and got nothing for Fog, nor Eset.

Fog client on laptop says it runs and finished Snapin OK, but nothing gets installed.

P.S. the command line works in CMD Admin no problem.

Any ideas?

@hammerc807 I actually never use sysprep and just deploy golden images. We do that exactly, the images are not domain joined and completely local workgroups and no AV installed.

Once imaged to a new laptop, we rename hostname, join domain and add AV and for some reason have issues with VPN

@george1421 Yes that’s right, DNS names of internal devices works okay, and also external sites within IP routing/CMD.

Browsing internet gives “Unable to connect” error.

No we have no proxy settings set on any of our browsers and simply uses our ISP’ connection. I have also removed our AV and is still the same issue which is strange.

After removing AV however, I am able to connect to shared drives which I find very odd. This does not happen on a normal user setup for Windows with AV installed.

Nevertheless still not able to connect to internet via browers. I am thinking, would installing pre-updates and driver updates in golden images may cause some kind of duplication of a deployed image?

I may try next is create another image with no latest OS and driver updates and see if that works okay with VPN and internet.

@george1421 Yes we also do not have our AVs in any of the golden images.

I did have issues with sysprep and prefer the setups we now use.

I actually ran the tracert to www.dell.com:

• VPN Disconnected:
  – Established connection to 104.120.212.17
  – Successfully connects going through hops

• VPN Connected:
  – Established connection to 23.72.62.221
  – Skips the initial internal IP addresses
  – Goes through the first public IP on 3rd hop which is our ISP’s network range
  – Then successfully connects going through hops
  – Also tracert to 104.120.212.17 and does same thing and eventually establishes connection

So with VPN connected, domain names are recognized through CMD but not using any browsers at all.

Possibly the internal firewall is blocking connection of web pages coming back onto the browser?

@george1421 Thanks for the response.

We do not use a sysprep image, just a normal up-to-date OS of the laptop with software and other config.

I would wonder if it would be related to the GUID, but we dont have a setting to to block already used GUID (if that can even be done), unless this is a default setting.

It works OK when it is deployed using a normal Win10 USB booty.

One thing I didn’t mention is, it (FOG deployment) actually does work initially with email, drive and internet access, but after awhile including disconnecting, and rebooting, the VPN connects as normal but no email, drive or internet access.

I would only ask whether sysprep might be the best option to completely have it’s own ID etc?

We have a working FOG server.

We have a batch of Dell Latitude 5330 laptops we are deploying and everything works including the Windows 10 Native VPN…however

When connecting to VPN, it connects to the company infrastructure with success and able to ping all internal IP addresses, and DNS names, but email access and shared drive access is not connecting whatsoever. Also bizarrely we cannot access internet.

Once we disconnect the VPN, internet works fine.

We have done the exact same configuration on the same laptop without FOG deployment.

Has anyone had any similar issues?