Thinkcentre M57p wont register

dwayneS

Currently running .32

Juan Antonio

It is very old, you should try to update your server to a newer version. I had the same problem with new computers in the network and solve it by updating to version 1.1.1 of FOG.;)

dwayneS

Thanx for the advice Juan. I came in this morning and ran the upgrade which went through smoothly. I did realize though why i may have had issues with the new computer and it might have happened to any machine i would have tried to edit. I realized when doing the upgrade the script showed me the server information which should IP and DNS settings that were no longer being used. I had recently done reconfiguration of the network and change the IP scope. I found this article [url]http://fogproject.org/wiki/index.php?title=Change_FOG_Server_IP_Address[/url] which stated things to change after an IP address change on the server. So maybe i has having the issue registering because the registration process would have been looking for the old IP address.

I think i’m almost done now. I do how ever need to change the IP address in the pxe boot file. I just tried to boot a machine via pxe and it showed that it was looking for the old ip address. I tried opening undionly.kpxe with gedit but the file does not open properly. How else can i change the IP?

dwayneS

Ok i did some more digging and found this post that gave me the solution to edit IP in pxe settings. I file i needed to edit was
[QUOTE]/tftpboot/default.ipxe[/QUOTE]

Source: [url]http://fogproject.org/forum/threads/fog-pxe-boot-error.10848/[/url]

I’m gonna now try to register a machine in the lab and upload the image. This will be my first windows 7 image so wish me luck

Juan Antonio

You can chage de FOG IP from fog configuration, fog setting, general setting,

[url=“/_imported_xf_attachments/1/1326_sshot-3.png?:”]sshot-3.png[/url][url=“/_imported_xf_attachments/1/1327_sshot-2.png?:”]sshot-2.png[/url][url=“/_imported_xf_attachments/1/1328_sshot-1.png?:”]sshot-1.png[/url]

Juan Antonio

What type of facility used for initial configuration of FOG?

dwayneS

I had to change the IP in these 3 places via fog web interface
[LIST]
[LIST]
[]General Setting: [B]FOG_WOL_HOST[/B]
[]TFTP Server: [B]FOG_TFTP_HOST, FOG_PXE_IMAGE_DNSADDRESS[/B]
[*]WEB Server: [B]FOG_WEB_HOST[/B]
[/LIST]
[/LIST]
After that i had to change the IP in the [B][I][SIZE=12px]/tftpboot/default.ipxe [/SIZE][/I][/B][SIZE=12px]file [/SIZE]
I don’t quite get you last question.

Juan Antonio

Your FOG works as DHCP server or is integrated into another network ??

dwayneS

Oh ok. Yes its integrated into network. Clients get IP from my Server 08 DC

Juan Antonio

Has FOG server static IP?
Did you set up in the DHCP server to redirect PXE requests to the IP of FOG? (Server 08 DC)

dwayneS

Yes all of that was done and was working OK from day 1. After making the changes I mentioned above all was well. I only have 2 issues now.

a section of my unattended file seems to not work. There is a command to enable the administrator account but that not working. I need to revisit.
The computer is not being joined to the domain via fog client service. When I check the log file I get an unknown error 2202.

Juan Antonio

Error 2202: from what I’ve read refers to the user name or group name parameter is invalid, you should check server settings.

What do you mean? about “a section of my unattended file seems to not work”

Juan Antonio

[URL=‘http://www.symantec.com/connect/forums/error-2202-user-name-or-groupname-parameter-invalid’]See this link[/URL]

dwayneS

Yes i had seen something like that. I need to check how server 2008 accepts the domain user credentials for user name.

I have a command in the unattend file that should enable the Administrator account. By default sysprep disables the Administrator account. So i need to revisit that section of my file

Juan Antonio

You can show unattended xml sysprep?

dwayneS

Here is my unattend.xml. After imaging the machine the Administrator account was still disabled and fog service still could not add machine to domain.

[CODE]<?xml version=“1.0” encoding=“utf-8”?>
<unattend xmlns=“urn:schemas-microsoft-com:unattend”>
<settings pass=“generalize”>
<component name=“Microsoft-Windows-Security-SPP” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<SkipRearm>1</SkipRearm>
</component>
</settings>
<settings pass=“specialize”>
<component name=“Microsoft-Windows-Deployment” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<RunSynchronous>
<RunSynchronousCommand wcm:action=“add”>
<Order>1</Order>
<Path>c:\windows\system32\net user administrator /activate:yes</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name=“Microsoft-Windows-IE-InternetExplorer” processorArchitecture=“wow64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<Home_Page>http://www.jamaicacollege.org</Home_Page>
<BlockPopups>yes</BlockPopups>
</component>
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ComputerName></ComputerName>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action=“add”>
<Password>
<Value>password</Value>
<PlainText>false</PlainText>
</Password>
<Description>Local Administrator</Description>
<DisplayName>Administrator</DisplayName>
<Name>Administrator</Name>
<Group>Administrators</Group>
</LocalAccount>
</LocalAccounts>
<AdministratorPassword>
<Value>password</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
</UserAccounts>
</component>
</settings>
<settings pass=“oobeSystem”>
<component name=“Microsoft-Windows-Deployment” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<Reseal>
<Mode>OOBE</Mode>
</Reseal>
</component>
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
<SkipMachineOOBE>true</SkipMachineOOBE>
<NetworkLocation>Work</NetworkLocation>
</OOBE>
</component>
</settings>
<settings pass=“windowsPE”>
<component name=“Microsoft-Windows-International-Core-WinPE” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
<component name=“Microsoft-Windows-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<WillShowUI>OnError</WillShowUI>
<Disk>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
<CreatePartitions>
<CreatePartition>

<CreatePartition>
<Order>2</Order>
<Type>Primary</Type>
<Extend>true</Extend>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>

<ModifyPartition>
<Order>2</Order>
<PartitionID>2</PartitionID>
<Format>NTFS</Format>
<Label>Windows</Label>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</component>
<UserData>
<ProductKey>
<WillShowUI>OnError</WillShowUI>
<Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</Key>
</ProductKey>
<AcceptEula>true</AcceptEula>
<FullName>Jamaica College</FullName>
<Organization>Jamaica College</Organization>
</UserData>
</settings>
<cpi:offlineImage cpi:source=“catalog:d:/sources/install_Windows 7 PROFESSIONAL.clg” xmlns:cpi=“urn:schemas-microsoft-com:cpi” />
</unattend>[/CODE]

Juan Antonio

It seems to be correct, do not know what can be the problem.

Juan Antonio

dof You set up the domain in FOG?

[url=“/_imported_xf_attachments/1/1329_sshot-1.png?:”]sshot-1.png[/url]

Jaymes Driver

[quote=“dwayneS, post: 36032, member: 25830”]Yes all of that was done and was working OK from day 1. After making the changes I mentioned above all was well. I only have 2 issues now.

a section of my unattended file seems to not work. There is a command to enable the administrator account but that not working. I need to revisit.
The computer is not being joined to the domain via fog client service. When I check the log file I get an unknown error 2202.[/quote]

Is this by chance an old image? I have had problems like this happen (with one unit in particular that we use for nComputing) where the Administrator user becomes corrupt and had to be removed. I also add a SECOND administrator when I use the unattend file, i name him Admin, that way I have two instances in which to enter as the admin user.

The only resolve I had for my issue was to set my image up again, it was daunting and well worth it!

I am glad you got your FOG issue fixed, and thanks for telling us HOW you fixed it, that will help users in the future, I hope you get your image issue fixed

Mentaloid

You upgraded to 1.2.0? If so, you might want to verify that the default domain settings are correct in FOG config, noting that the domain portion should NOT be included in the username anymore.

If you have clients that are not using the default (as in you specified the OU, and therefore the rest of the domain settings as well), then you may need to double check the individual clients/groups as well for misconfigured domain/user’s

Thinkcentre M57p wont register

151

11.8k

17.2k

154.9k