@george1421 Thank you for the quick reply! As a follow up, I managed to update to 1.4.0 RC6 and was then able to deploy an older image without trouble (single disk - resizeable). It completed, and resized successfully. Take care!
R
Best posts made by rmmadden
-
RE: No source file passed (writeImage)posted in FOG Problems
-
Normal Snapin deploy .reg fileposted in Windows Problems
Server
- FOG Version: 1.4.0 RC6
- OS: CentOS 6
Client
- Service Version: 0.11.12
- OS: Windows 7 64
Description
I have recently upgraded our FOG server from 1.2.0 to 1.4.0 RC6 (by way of 1.3.5, which needed to be upgraded for a bug that 1.4.0 RC6 solved). I have tested almost everything functionaly except for some of our snapins, which we use to deploy registry updates (for some autologon stuff). Everything seems find on the server end, as well as on the client end, but when the snapins deploy, none of the registry changes are affected. The fog.log on the client shows successful text, with regedit returning a 0 which means success. The same .reg file, run locally, applies fine - it just seems like it isn’t able to run as a snapin through FOG anymore.
In terms of snapin configuration, I have been using the the Run With “regedit.exe” with the argument “/S”
example: “regedit.exe /S autologon.reg”We don’t use snapins for anything else, so I am not sure if this is an issue with snapins in general, or just these .reg ones.
Has anyone gotten .reg files to deploy successfully on these current builds? If so, how are you doing it? Thanks all!