linux Operating System Deployment

error when copying or overwriting the same directory name linux

my directory structure in linux – centos:


/wordpress/ is my wordpress install, and /update/ is my unziped download files and directories.

The errors I kept getting when trying to move or copy the entire directory while sitting in /home/html/prod/wordpress/update/ was:

mv: cannot move `wp-admin’ to a subdirectory of itself, `../wp-admin’
mv: cannot move `wp-content’ to a subdirectory of itself, `../wp-content’

cp: omitting directory `wp-admin’
cp: omitting directory `wp-content’

what I ended up doing was staying in the same directory ( /home/html/prod/wordpress/update ) and running:

cp -fR * ../

f = force
R = recursive

all went well, replaced the entire directory like I wanted and I just removed the /update directory and done.

Landesk Operating System Deployment

Make Service Tag the Computer Name in Landesk OSD

We use service tags as our computer reference, and how we join our computers to the domain. I needed to have Landesk automate this for me, so I wanted to have ot pluck the information from BIOS. This is what I added to the script.

When you’re creating/editing your deployment script you need to make sure the $MAC is in the SysPrep options -> Naming convention :

[zp src=”osd-sysprep.png” album=”blog/Landesk/” width=”600″]

Once the deployment script is created, right click advanced edit (This works for XP and Windows 7 scripts, be sure to use corresponding line though)

[zp src=”osd-servicetag.jpg” album=”blog/Landesk/” width=”600″]

You will then replace the line REMEXEC34 with the following :

Windows 7:
REMEXEC34=ldrun tokreplw C:\unattend.xml COMPUTERNAME=%Computer – System – Serial Number%

Windows XP:
REMEXEC34=ldrun tokreplw C:\sysprep\sysprep.inf COMPUTERNAME=%Computer – System – Serial Number%

Copy over the new script into your PXE, and you should be good to go. This will automatically put in the service tag into the computer name.

Landesk Operating System Deployment

Windows XP – Remove 30 second time with Landesk OSD

I kept running into an issue where Windows XP would add a 30 second boot time, and I disliked have to manually go in and change it after the computer was done imaging. So with Landesk OSD this is what I did to fix it in the script.

Browse out to: \\landeskcoreserver\ldmain\landesk\files
edit the file *.inf example file name : XPDeploy-ACCOUNTING.inf
add this line: Command6=”bootcfg /timeout 0″
you’ll need to change the Command6 number accordingly to how many commands precede already. I added mine to Command6

Operating System Deployment


I recently formatted my IBM x220 into IDE on accident, and wanted to change it from IDE to AHCI. This was a simple procedure, noted by MS :

  • Exit all Windows-based programs.
  • Click Start, type regedit in the Start Search box, and then press ENTER.
  • If you receive the User Account Control dialog box, click Continue.
  • Locate and then click one of the following registry subkeys:
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV
  • In the right pane, right-click Start in the Name column, and then click Modify.
  • In the Value data box, type 0, and then click OK.
  • On the File menu, click Exit to close Registry Editor.
  • Now as you reboot, make sure to change it to AHCI in BIOS, and voila, all should be working.

    Operating System Deployment

    WinPE automatic windows 7 activation

    We run Landesk, using the HII (Hardware Independent Imaging), which is run within a WinPE environment. I ran into issues where Windows 7 would not auto activate, which was causing issues, as some of the techs were forgetting to activate windows 7. We have a lot of internet restricted users, so once logged in as that use, they would not be able to get activated themselves. What I found was very simple.

    The fix :

    On your windows 7 image, browse out to : C:\Windows\Setup\Scripts\ and create a file called SetupComplete.cmd. In that file, you want to put in :

    cscript C:\Windows\System32\Slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
    cscript C:\Windows\System32\Slmgr.vbs /ato

    You will want to put your CD Key in the area where x’s are. Now sysprep, and roll out a new build!