Topics created by hernani

@hernani In domain moves you are better to stick to the Windows world for this action. You can use FOG to deploy vbs/ps/cmd file that changes the target computer’s affiliation. You will have less issues if you do this in the windows realm.

For one deployment I setup the computers where initially put in one Imaging OU that had no GPO policies that would break imaging. Then in the first run part of the unattend.xml file I ran a VBS script called move to OU to relocate the target computer to the proper OU. Now this was not moving to a different AD domain, just to a different OU.

I think there was a netdom command that we used at one time to join computers to domain (not by using fog). That utility had the ability to connect and disconnect a device from domains.

One other thing you need to keep in mind is make sure you have a local admin account on the target computer you can use if the domain move fails, otherwise your target system will be lost if the reconnect to the new domain fails.

@hernani First I would recommend that you update your version of FOG. you are on 1.5.9RC2. I would at least go to 1.5.9 or even better once at 1.5.9 switch to the dev-branch and move up to 1.5.9.111.

If you use the git method to install FOG then just switch to the /root/fogproject directory and do a git pull command then switch to the bin directory and rerun the installer ./installfog.sh script again.

After that if you want to upgrade to the dev-branch you can issue these commands.

cd /root/fogproject git checkout dev-branch git pull cd bin ./installfog.sh

That might not take care of this issue, but at lest if you are on the latest release the devs can help you.

Typically when we see this problem at the end of capture with an ftp error message its because someone changed the fogproject linux user account or password. The memory exhaustion issue might be addressed in the update. I know I’ve seen this error before quite a while ago.

Yes SVN method has been removed, only the git and tarball method is actively supported now.

https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG

This process is recommended for new installs as well as upgrades to existing installs.

@george1421 ah, that’s right. i forgot about that. that would make his version a month or two before the first 1.3.0 RC build. there shouldn’t be any problems with upgrading that.

@Sebastian-Roth This is what I am seeing:
Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted
Synchronizing state of mysql.service with SysV init with /lib/systemd/systemd-sysv-install…
Executing /lib/systemd/systemd-sysv-install enable mysql
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted
Operation failed: No such file or directory
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted
Operation failed: No such file or directory
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted
Failed to get D-Bus connection: Operation not permitted

@Tom-Elliott
Indeed, last week was 7575 i think (but not sure) but now everything is ok.