Hi,

We are facing network related problem while deploying Window 7 image through Altris ( ver 6.9) on WinXP machine.

Post deployment, the machine is taking IP address 169.254.112.42 instead of predefined IP address mentioned in the image.

We strongly feel that this is something to do with registry setting.

Request you to guide us on how to reslove this issue.

All help on this front is appreciated.

You can prevent a computer obtaining an APIPA address by following the instruction below.

http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/how-do-i-disable-automatic-private-ip-addressing/1c9044d2-85a5-4cb2-ba90-ff6866a4adb1

Hello ISmicro,

Does the predefined IP address is static or came from DHCP server?

Please take the following steps for troubleshooting:
1. If you deploy the same image to several computers, please check if the predefined IP address is same.
We could use normally computer to ping the IP address and check if it is in use.
2. If you use the DHCP server to assign IP and network information, please check if there are still IP address in the DHCP pool.
3. If you have the DHCP relay agent, please check if it is correctly configured.

As the issue is related to Altris, please contact the related support to check if there are misconfiguration.

Best regards,
Fangzhou CHEN

Dear Fanzhou CHEN,

The testing is carried out in a DHCP enviornment. We make it a point to disable DHCP and its dependent services on the target machine. However, when the system boots, it automatically enables DHCP service and assigns the IP. Is there any other automated way to disable the system from picking up an IP other than what we want it to take?

We got the Altiris configuration checked and did not come across any issues.

Dear Fanzhou CHEN,

The testing is carried out in a DHCP enviornment. We make it a point to disable DHCP and its dependent services on the target machine. However, when the system boots, it automatically enables DHCP service and assigns the IP. Is there any other automated way to disable the system from picking up an IP other than what we want it to take?

We got the Altiris configuration checked and did not come across any issues.

Hi ISmicro,

Are you able to change your image? in that case disable the DHCP client service before you capture the machine. then the DHCP client service should not be able to start and you would get no IP adress on the host.

Though, not sure why you don't want to use the service and assign it manually (you could use reservations if you want it to obtain a certain address)

how are you pre-defining your address. i think that is where you should look for the answer, since it is probably that part that isn't working correctly

Regards
Johan

• Proposed as answer by FangZhou ChenMicrosoft contingent staff, Moderator Tuesday, January 27, 2015 1:51 AM

Hello ISmicro,

You dont want to use DHCP to assign IP address?

I agree with Johan. If the Altiris pre-configured IP address has conflict with other computers, there will be IP address like 169.254.X.X.

Best regards,
Fangzhou CHEN

Dear Johan,

I did change the image by disabling the DHCP (and its dependent) client services before capture. Despite this, system does not take defined IP. Post image deployment it starts the DHCP services on its own and assigns an IP.

I need to deploy in a non-DHCP enviornment. However, my test enviornment has DHCP.

The pre-defined IP address is a valid IP address.

Regards

 

Hello Fangzhou,

My target deployment enviornment is non-DHCP.

The pre-configured IP is an available one (not assigned) which is verified before assigning.

Please advise.

Regards

Hello ISmicro,

As this deployment is from Altris, please check with manufacturer about the IP configuration in the deployment.

Best regards,
Fangzho

Dear Fangzhou/Others,

Appreciate the responses.

Further on this issue, I was able to test on a desktop in a non-DHCP enviornment and it worked. I need to do this for other machines before coming down to a conclusion.

However, I am facing issues while deploying on a POS. I tried deployment on a POS machine and it failed - again in same non-DHCP enviornment.

Any insights/inputs on POS front?

Regards

IS