Posts made by Jaymes Driver

try setting the image type to “windows xp”.

Dual boot upload has worked in the past.

If this fails, use the RAW disk type.

Sorry to hear about the complications with the drives. Tom is working hard to try to include the newer hardware in the latest revision. I agree with Tom, if you would like to see how FOG is progressing download the 0.33b revision.

I have used it to image a few test machines with the GPT format, it’s not a perfect solution yet, but hey maybe you can help us find the snags and resolves for them!

Did you try another kernel as Tom suggested?

I would use this link now though the one he has listed is the 64bit Kernel now.

[url]https://mastacontrola.com/fogboot/kernel/bzImage32[/url]

[quote=“mOrloff, post: 23798, member: 22660”]Before I pull any triggers, please confirm whether I’m interpreting correctly.
It sounds like the flexibility is there to work with whatever type of hdd arrangement I want, which is super cool.[/quote]

ABSOLUTELY!!! FOG is very flexible. Currently it doesn’t exactly LIKE to image windows 8 but we have it working so all in due time

As far as building your image… I would build a dualboot machine in a Virtual format and use that to deploy. Imaging is like taking a snapshot of the hard drive and copying it over. I like FOG because I can set up my machines so that after I install FOG it names my machines conventionally, activates windows, and installs my drivers all without my attention. (Of course it took a LOT of attention to get it to this point)

If you were using a live CD to install linux on the same hard drive as a Windows installation I would say that method is plausible. However given the nature of FOG and how others like the “zero touch” method of installation, I would not expect to image this way as you are talking about installing an image on a hard drive that is already in use and doing so will ruin the data currently installed on it and it would leave a linux install.

If you can automate the installation process of linux and tweak it to your standards, you can include an iso image as a bootable option that would allow you to install the linux distribution after the windows imaging process.

If I were going to try this in my environment, I would set up a machine exactly how I want it to be after imaging and I would upload that entire hard drive image to my FOG server.

If you want to just TEST linux deployment with FOG, then creating an image and pushing it to a machine would allow you to troubleshoot errors you may encounter with the Linux portion, but the end result will be a hard drive with ONLY linux installed.

I hope this helps I would be more than happy to explain more!

In the future, please put all your “Pasting” into code brackets that way it won’t convert some of the code to smiley faces like

That and it helps to define what is the information pasted from the server, it differentiates what steps you have tried, and it outlines the error without having to thumb through the settings to get to where the issue actually lies.

I don’t know too much about the solaris system you are coming from BUT… Others in the past have had to deploy an image using their OLD imaging solution to a machine and immediately (WITHOUT BOOTING THE OS) upload the image to FOG, this will give you an exact replica, and it puts it in the format FOG knows how to interpret.

Did you register a machine as a host to the fog server (sorry silly questions but I want to make syre we are on the same page)? Have you set up an Image store on the FOG Server under Image Management? Did you assign an OS type to the image? Did you also assign the image to the machine registered as a host on the FOG server?

Did you add a .mntcheck to the server store?

[code]
sudo touch /Tools/ .mntcheck
sudo touch /Tools/BuildFarmImages/ .mntcheck
[/code]

Did you add FOG as the owner for the directory?
[code]
chown -R fog.root /Tools/BuildFarmImages
[/code]

Did you edit your etc/exports to reflect the changes in the image store?
[code]
/mnt/Tools/BuildFarmImages *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/mnt/Tools/BuildFarmImages/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
[/code]

It would be wise to create the /dev folder and give FOG full red and write access as it will upload the image to this temp folder then copy it to your image store.

Tom knows quite a bit more about the NFSMount options perhaps he will offer some expertise here.

Welcome to FOG!

The good news is, FOG can work with machines that have multiple OS’s on them. Unfortunately I have not ventured into the realm yet, so I can’t offer any expertise as of moment. I just wanted to let you know that others on the forum have accomplished the task.

Some linux revisions that use Grub2 will not be entirely happy, a work around for this is to downgrade the GRUB utility. But I don’t know if this information holds true to the FOG 0.33b currently in development. That is a question we need to reserve for Tom Elliot.

FOG has the ability to work with multiple disks, and multiple partitions, you have to tell the FOG server how to expect the image to come, such as: Single Partition, Multi-Partition Single Disk (I would use this option if I were to dual boot and use a single hard drive), Multi-Partition All Disks, and RAW.

Raw takes a copy of the drive exactly how it sits with no compression, it has been useful in the past for others but should be a lst ditch effort.

My recommendation for you is… Set up a virtualized FOG server, that way you can become familiar with the Web GUI and the server itself. You can begin troubleshooting your environment and fine tune the settings so that machines can PXE boot the FOG Server. After you are comfortable with the server, I would do a basic install on a hard drive with Windows and Linux as a Dual boot. Register the machine to the FOG Server and test an upload and deploy. If you have issues we can help you to troubleshoot them to get your image working as expected. After you spend sometime and feel comfortable using FOG as an imaging solution, I would build my image for my machines install all updates and then push the image to the server and test a deploy. Personally I use Virtualized machines to build my images on, as I can set up an image that is not dependent on drivers and I inject them later, but I would begin thinking about how you will build your images now.

Any changes you make to your image will not be affected on the server until you update the image store on the server with a current back up by choosing to “Upload” your image to the server. Nothing done to images, updates or installations, will be consider “automatically” by FOG. FOG doesn’t have the ability to look at raw images, determine the differences, and toss out an old image for a new one.

Exactly as Tom says. Good luck.

VincentJ you can name them as you want, but I set the fog service to rename them, and if they don’t meet my naming scheme I track them through a management software, a couple of them really, so I can see the Host name assigned to the machine.

I check all of this and even fix it if necessary, which has only been the case on like 4 machines, and then I activate my windows. Everything I do is tied to a user log in, it registers everything to my novel tree and context, names the computer, enables novel auto log in (which heavily depends on the host name of the machine) then it activates windows.

I will do you a solid and just post my Unattend.XML

Please note that the key listed here in my unattend file is a generic key, I activate to my KMS server after installation this just gives the install a key so it can continue.

[code]
<?xml version=“1.0” encoding=“utf-8”?>
<unattend xmlns=“urn:schemas-microsoft-com:unattend”>
<settings pass=“windowsPE”>
<component name=“Microsoft-Windows-International-Core-WinPE” processorArchitecture=“x86” 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=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<UserData>
<AcceptEula>true</AcceptEula>
</UserData>
<EnableNetwork>true</EnableNetwork>
<EnableFirewall>false</EnableFirewall>
</component>
</settings>
<settings pass=“specialize”>
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ShowWindowsLive>false</ShowWindowsLive>
<ComputerName>*</ComputerName>
<RegisteredOrganization>Microsoft</RegisteredOrganization>
<RegisteredOwner>AutoBVT</RegisteredOwner>
<ProductKey>KEY GOES HERE</ProductKey>
<CopyProfile>true</CopyProfile>
<TimeZone>Eastern Standard Time</TimeZone>
</component>
<component name=“Microsoft-Windows-TerminalServices-LocalSessionManager” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<fDenyTSConnections>false</fDenyTSConnections>
</component>
</settings>
<settings pass=“oobeSystem”>
<component name=“Microsoft-Windows-International-Core” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<InputLocale>en-US</InputLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<SystemLocale>en-US</SystemLocale>
<UserLocale>en-US</UserLocale>
</component>
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<AutoLogon>
<Enabled>false</Enabled>
<LogonCount>1</LogonCount>
<Username>administrator</Username>
<Domain>Redding</Domain>
</AutoLogon>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>MAB3AGwAMQA2ADMAOABBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAFAAYQBzAHMAdwBvAHIAZAA=</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action=“add”>
<Description>Local Administrator</Description>
<DisplayName>Administrator</DisplayName>
<Group>Administrators</Group>
<Name>Administrator</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<RegisteredOrganization>Seymour Community Schools</RegisteredOrganization>
<RegisteredOwner>Seymour Community Schools</RegisteredOwner>
<VisualEffects>
<FontSmoothing>ClearType</FontSmoothing>
</VisualEffects>
</component>
</settings>
<settings pass=“generalize”>
<component name=“Microsoft-Windows-Security-SPP” processorArchitecture=“x86” 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>0</SkipRearm>
</component>
</settings>
<cpi:offlineImage cpi:source=“wim:d:/sources/install.wim#Windows 7 PROFESSIONAL” xmlns:cpi=“urn:schemas-microsoft-com:cpi” />
</unattend>
[/code]

Try a different kernel, those bios errors don’t mean beans.

yes. Tom keeps this kernel up to date.

Back up your old bzImage. located /tftpboot/fog/kernel/bzImage.

Change it to bzImage.OLD or something similar.

Download the new bzImage from [URL=‘https://mastacontrola.com/fogboot/kernel/bzImage’][COLOR=#737373]https://mastacontrola.com/fogboot/kernel/bzImage[/COLOR][/URL]

put the new bzImage in the /tftpboot/fog/kernel/ folder.

[quote=“Tom Elliott, post: 23612, member: 7271”]r1262 released.

Fixes Windows 8 and below imaging issues. Yes this includes UEFI/GPT disks. You will need to disable secure boot on the drives but all seems to work. You may even (which I might fix myself) randomize the GUID of the disk to get booting to work as well. Hopefully this helps, and it’s very exciting.[/quote]

Nice job Tom!

Now I just wait to hear those dreaded words “Get Windows 8 installed on all the staff and student machines!”

Ty9000, this is a common problem when imaging.

I ALWAYS use a virtual set up with a ~30GB drive, (you can’t find anything smaller than that online unless you REALLY try, and with the price of drives today why would you pay the extra cash for a small drive?), this way I can expand the partition to fill up the rest of the disk space, and I know that I won’t run into issue putting the image on a smaller drive.

I know this probably doesn’t help you much now, but in the future remember that you can take a smaller image to a large drive, but you can not take a larger image to a smaller disk regardless of how “big” fog thinks the image is.

Please explain deeper I don’t quite understand what it is you are asking.

Are you asking where fog stores it’s information so you can back it up? Are you wanting to turn off the “fog” portions of the server?

This is a known issue with the 12.04 Ubuntu derivative, the services are started before an ip address is assigned to the machine.

There are a number of posts ON THIS FORUM that explain how to rectify the issue and delay the start up of the job so that you don’t have to start them manually after each reboot.

Use dnsmasq to set up ProxyDHCP service. I had to do this in my network operating on a Novell Newtork. We have a WDS at some other locations and we had helper ips added to help get the imaging to the other buildings. This in turn over writes your settings in your DNS/DHCP area where you have set the fog server ip address.

I found that enabling the proxy dhcp server allows me to FIRST boot my fog server, and if I turn my fog server off I can still image via WDS. It is a win/win situation.

Use DNSmasq.

I work in an environment where each tech has a certain number of buildings, and we get to manage and image each the way we choose. My other tech who was here before me set up the WDS, so I KNOW it is still in use as he is still here, so disabling any services on the WDS was not an option for me.

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]

Give this a try, this is the kernel Tom Elliot keeps updated.

back up your bzImage by renaming it to bzImage.OLD and copy the new bzImage to the folder.

TFTP service is part of the FOG server, so yes your FOG server is your TFTP server. This isn’t always the case, some corporations have their own TFTP server and you can use that in place of the one provided by FOG, in which case, you would tell FOG where your TFTP server is located, i.e. it’s ip address.

For further assistance, please refrain from making multiple posts about the same issue.

[url]http://fogproject.org/forum/threads/pxe-boot-with-a-dell-optiplex-760.10076/#post-23466[/url]

Yes, windows makes a copy of the sysprep file to C:\Windows\Panther. This is the file actually used by the OOBE process after imaging.

I believe it is copied from the sysprep folder during the sysprep process, if memory serves me correctly.

Not necessarily, but if you keep topics down we can help troubleshoot the issue, the more topics you have open the harder it is to consolidate the troubleshooting steps you have taken as well as the resolve.

To answer your question in the other topic, Yes in fog the TFTP server is the same machine that FOG runs on, however this is not required. You can always supply your own, but FOG was an aim to get everything you need workign in one places.

In your other topic you stated you were running the “latest” fog version. Please clarify, Are you using FOG 0.32 or FOG 0.33b?

I am leaving Note that you are using CentOS 6.5

From a windows machine please run the following command in a command prompt

[code]
tftp x.x.x.x get pxelinux.0
[/code]

what is the outcome?