Topics created by Steve Ropiak

This is my last day at this location. Giving up on this and moving on. Thanks to everyone who offered assistance along the way.

Apparently, had not re run installfog.sh after starting nfs. Tried that first and the error. So, I ran the commands above and still get the error. Just in case, I did re set the password for the Fog user to match the Fog settings in the gui. Also checked permissions of /tftpboot and it is 0755 and the owner is Fog.

no problem.

No, all my experience is with FOG 0.32 at this time. As far as FOG goes, the only thing different about Windows 8 is that I choose Windows Vista as the OS type and Multiple-Partition, Single Disk (non-resizable) for the image type.

Downloaded and unpacked the newest Fog to get Fogcrypt and it works. Thanks to everyone for their helpful suggestions.

Chad as a side note to your statement. I have NetBios blocked on our domain and it still works.

[quote=“Steve Ropiak, post: 11276, member: 47”]If I run sysprep with an unattend.xml that does everything except name the computer (it prompts for that), when exactly does this script run? Is it after the mini setup is totally done? I’d like to populate this with my little powershell script that joins the domain, sets a password and activates the real administrator account, etc. Basically what I need to know if this is the last thing to execute. Thanks to all who reply.[/quote]

The stages for Windows deployment/installs can be found here:

[url]http://unattended.msfn.org/unattended.xp/[/url]

Not much has changed really in the timing of when things happen. As far as the last thing that runs, that is the RunOnceEx.cmd. It will launch anything under the system account. It still works for Vista, 7 and 8 as I’ve used it for remote users that are on dial up to send an all in one distribution with slip streamed patches and applications.

For bare metal maintain a list somewhere that a net command can fetch a name from (csv, txt), can’t find the script in the pile I have right now, but this should get you headed in the right direction. It still works for Vista and 7 incidentally. I haven’t tested it for 8 because the places I contract to are seriously looking at Ubuntu with WINE because…well, just look at 8. It’s pretty awful.

Otherwise, munge the vbscript as much as you like and it will be the LAST item on the RunOnceEx.cmd because it requires a reboot.

[SIZE=12px][FONT=Verdana][COLOR=#070f14]'Changing computer name for WNT/W2k/WXP with script:[/COLOR][/FONT][/SIZE]

[SIZE=12px][FONT=Verdana][COLOR=#070f14]sNewName = “put new name here”[/COLOR][/FONT][/SIZE]

[SIZE=12px][FONT=Verdana][COLOR=#070f14]Set oShell = CreateObject (“WSCript.shell”)[/COLOR][/FONT][/SIZE]

[SIZE=12px][FONT=Verdana][COLOR=#070f14]sCCS = “HKLM\SYSTEM\CurrentControlSet”[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#070f14]sTcpipParamsRegPath = sCCS & “Services\Tcpip\Parameters”[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#070f14]sCompNameRegPath = sCCS & “Control\ComputerName”[/COLOR][/FONT][/SIZE]

[SIZE=12px][FONT=Verdana][COLOR=#070f14]With oShell[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#070f14].RegDelete sTcpipParamsRegPath & “Hostname”[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#070f14].RegDelete sTcpipParamsRegPath & “NV Hostname”[/COLOR][/FONT][/SIZE]

[SIZE=12px][FONT=Verdana][COLOR=#070f14].RegWrite sCompNameRegPath & “ComputerName\ComputerName”, sNewName[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#070f14].RegWrite sCompNameRegPath & “ActiveComputerName\ComputerName”, sNewName[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#070f14].RegWrite sTcpipParamsRegPath & “Hostname”, sNewName[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#070f14].RegWrite sTcpipParamsRegPath & “NV Hostname”, sNewName[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#070f14]End With ’ oShell[/COLOR][/FONT][/SIZE]

[SIZE=12px][FONT=Verdana][COLOR=#070f14]MsgBox “Computer name changed, please reboot your computer”[/COLOR][/FONT][/SIZE]

If doing an in place migration of MS OS products:

What you should be asking is how do I backup meaningful data before wiping the box?

The OS and apps are one thing, but end users usually are more than a little annoyed when all their stuff is gone. Read up on USMT (User state migration tool), for FOG I would use USMT v2.0 or lower as the initialization of the deployment process. Either by command line or using the automatic UI agent.

USMT is a pile of scripts made by microsoft that go hunting for user generated stuff (docs, pics, music, video) and put it somewhere else (attached storage/USB/NAS). Later versions use the MS certificates and are very painful to get working properly without Active Directory and a file share structure/SCCM available to manage it. So word to the wise, don’t count on any version of USMT to work outside of SCCM 2007 or 2013, even then WITH SCCM it is very painful to setup.

OK, thanks for clearing that up. I was confusing 0.32 with 0.33

I did get that error and, on a whim, checked permissions on the /images folder. As it turns out, only root had write permissions there. Once I corrected the permissions, all is well. Thanks for the post. Everyone here is great.

I do see both the 100 MB and the other partition. I selected Multiple partitions, not resizeable and I ran tests with the other options except RAW and those failed as well. I’m thinking that there is something odd about the way the tech built this one because I can’t use CloneZilla live on it either. I think I’ll reload the drive and try to upload it again. It’s easy enough to do. Thanks for posting.

Great stuff. We’ll be using Fog for a Win 7 deployment over the summer. What is this sleep? Everyone talks about it, but i can never seem to find any at work. 🙂 Thanks for your post.

It’s not exactly what I had hoped i could do, but it’ll get me where I need to go. Thanks!!

Now that I’ve had time to watch the entire video, I have a question. What does the sync process do? Does it make the image files from the storage node accessible to the main server without transferring the actual file?

Thanks,

Steve

It could use some cleaning, but this is the jist.

[quote=“Blackout, post: 2155, member: 1”]To fix the timezone issue, edit your php.ini and set the ‘date.timezone’ variable.

The installer does not use ‘php -v’ to check the version, it queries RPM.
Run this for me and post the output:
[code]rpm -q php53[/code][/quote]
Odd, on my base server php -v sez I have version 5.1. If I do an rpm-q php51, it said not installed, BUT if I try rpm -q php it correctly identifies 5.1 as the version. i also noticed that the wiki doc states in the CentOS install that it was tested with 0.30. Has any testing been done with 0.32 and CentOS or am I performing that function. 🙂

The PHP upgrade for CentOS is brutal. I have no idea why they have not upgraded to 5.3, or even 5.2.

Please see the comments on CentOS 5.6 (at the bottom) on how to manually upgrade PHP to 5.3
[url]http://fogproject.org/wiki/index.php?title=Installation_on_CentOS_5.3[/url]

If this is your first FOG server, i [I]really[/I] recommend Ubuntu. APT’s package management is far superior to YUM’s.
The package maintainers for APT packages are standards nazis; they adhere to a very strict set of standards.

Checking the packages for PHP5 from Ubuntu/Debian shows 5.3.8 is the latest version.

[code]fog-2:~# apt-cache policy php5

php5:
Installed: 5.2.6.dfsg.1-1+lenny4
Candidate: 5.3.8.0-1
Version table:
5.3.8.0-1 0
500 http://ftp.iinet.net.au testing/main Packages
5.2.6.dfsg.1-1+lenny13 0
500 http://security.debian.org lenny/updates/main Packages
*** 5.2.6.dfsg.1-1+lenny4 0
100 /var/lib/dpkg/status
[/code]