Quantcast
Channel: Symantec Connect - Ghost Solution Suite - Discussions
Viewing all articles
Browse latest Browse all 1315

169.X.X.X IP network address after imaging

$
0
0
I need a solution

Hi All, 

Server 2019 running GSS 3.3 RU2 

Problems after imaging

Any images that were created before the new server rebuild (last week of december) can be used to image a PC and it goes through the config, joins domain, completes tasks and works

Any new images (created since the rebuild - last 2 weeks) the image will create with no issues - but when pushed to any other PC, it images fine but stops at configuration point with no error (windows 10 1809) 

When logging in locally it has a 169 internal network address

Checked drivers, uninstall, reinstall still no ip address, no issues in device manager, card reported as working (its as if it cant connect to DHCP server) 

Tried using exisiting image create jobs and recreating the create job , tried pushing and pulling from different PCs but outcome is always the same - 169 address

Ive chekced everything I can think of and tried everything

Aside from reinstalling everything again on the server I was wondering if any body had any ideas ?

I have checked in the temp folder on express on 2 servers and only difference I cam see when comparing cfg files is a line 

not working server line

SetIPInfo=True
Route0=0.0.0.0         ,0.0.0.0         ,10.110.1.250    ,                ,1,                ,0,0
Static-Route-Count=1

working server line

SetIPInfo=True
Static-Route-Count=0

If this is the cuase im not sure where to make the changes to it? 

We have 4 other servers on other sites, all identical and all working 

Thanks

0

Viewing all articles
Browse latest Browse all 1315

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>