Pages

Showing posts with label deploy. Show all posts
Showing posts with label deploy. Show all posts

Wednesday, 17 July 2013

Upgrade Microsoft OCS 2007 to Lync 2013 in a Windows 7 x86 environment using SCCM 2007: Part 2

Continued from Part 1

Compressing the Lync Client (cont...)

You will now have a folder called Microsoft_Lync_2013_x86_01 containing:









  • This is now the source folder we will point our SCCM package to.  
  •  You will now need to create a program in the package and point it to the TSINSTALL.bat

Creating the Task Sequence

There were several factors involved in my choice to use a task sequence to do this.  Mainly because we can run command lines directly from the TS rather than having to come up with a massively long boring script.

  • Create a new task sequence under the Operating System Deployment section of SCCM
  • Choose "create a new custom task seqeunce"
  • Name it Install Lync 2013 x86 and click finish
  • Add an Install Software step and call it Install Microsoft Lync 2013 x86
  • Choose the package and program you created earlier (an assumption)
  • Create a run command line step to kill of the Communicator process.  Name it Kill Communicator Process and use the command: taskkill /im communicator.exe /f
  • Create a run command line step to kill of the Outlook process.  Name it Kill Outlook Process and use the command: taskkill /im outlook.exe /f
  • Create a run command line step called Remove Live Meeting with the command: MsiExec.exe /X{A98AFBC7-D5A7-46A1-8795-EABE2F55A7D6} /qn REBOOT=ReallySuppress
  • Create a run command line step called Remove OCS 2007 with the command: MsiExec.exe /X{E5BA0430-919F-46DD-B656-0796F8A5ADFF} /qn REBOOT=ReallySuppress
  • Create a run command line step called RemoveOutlook Plugin using the command: MsiExec.exe /X{1DE3088D-E607-4EB0-9223-106E7B5AF2F1} /qn REBOOT=ReallySuppress
  • Create a run command line step called Delete Source Files with the command del c:\lync2013x86 /F /Q - run this step with an admin account as per the tick box at the bottom.
Your Task Sequence should look this this.
*I ticked "Continue on error" in the options tab on every step EXCEPT the install Lync step.




Click OK to save the Task Sequence.

Now advertise the task sequence out to a collection - I advise not populating the collection yet - just test this on 1 computer for now and then add a few more once your happy it's working the way it should.  Tailor the advertisment in as way to suit you; Silently or with an on screen prompt etc. ASAP or a timed schedule...

I AM NOT RESPONSIBLE FOR YOUR CHOICES OF TARGET - DON'T BLAME ME IF YOU TRASH YOUR ESTATE WITH THIS METHOD!!!

This is what will happen.

  1. Target computer will recieve policy from SCCM
  2. TS will launch and copy over source folder
  3. Program will run which will create the extract source, extract the 7z install and run setup.exe
  4. Once Lync has installed the TS will kill off OCS & Outlook
  5. It will remove Live Meeting, OCS and the Outlook Plugin
  6. Source files are deleted.


I really hope this works for people and I welcome any constructive comments....

docN

Upgrade Microsoft OCS 2007 to Lync 2013 in a Windows 7 x86 environment using SCCM 2007: Part 1

As part of our ongoing commitments to optimise our users desktop experience; our infrastructure team are currently implementing a Lync back end.  Of course it comes to me to package and deploy the client out to our estate.  As we are currently running a mixture of XP and Win7/8 there is a different method required for XP.

In this post I will explain how I went about packaging up Lync so it would remove any legacy installs of Office Communicator and replace it will Lync.

This is going to be a lengthy one so make coffee - LOTS of coffee.  Hopefully though it will help other people to achieve the same as me should that be what they require.

You will need the following:

Lync 2013 x86 client (I downloaded the ISO from our VLSC)
7zip (executable AND command line) http://www.7-zip.org/

Assumptions:

  • You are proficient in SCCM 2007 packaging and deploying
  • you have used the OCT to customise Office installs
  • You require a silent install 


Packaging the Lync client

Customising the install

Assuming you have the above we will first setup the Custom.MSP file via the OCT.  Once you have extracted the ISO your file structure will look like the above.  You will not have the "Admin" shortcut so we create that now.


  1. Right click "setup.exe" and click "create shortcut"
  2. Rename "setup.exe - shortcut" to "Admin"
  3. Right click "Admin" and at the end of the Target path you need to add "/admin".  Mine looks like this: "\\MYSCCMSERVER\Packages\Microsoft_Lync_2013_x86\setup.exe" /admin
  4. Click OK
  5. Double click Admin and you will be prompted to create or open an MSP file - just click OK to create a new one.
  6.  Under Setup, click Install location and organisational name - enter your org name here.
  7. Under Licensing & User Interface choose your method of entering the product key - I use KMS.
  8. Click I accept the terms... box, change display level to "none" and tick suppress modal
  9. Under "Additional content" click "Add registry entries" and add the following:
  10. Machine setting
    1. Root : HKEY_Local_Machine
    2. Type: DWORD
    3. Key: Software\Policies\Microsoft\Office\15.0\Common\General
    4. Name: ShownFirstRunOptin
    5. Value: 0×00000001
  11. User Setting
    1. Root : HKEY_Current_User
    2. Type: DWORD
    3. Key: Software\Microsoft\Office\15.0\Common\General
    4. Name: ShownFirstRunOptin
    5. Value: 1
Once you are happy that you have customised your install accordingly click "file" "save as" and save the file into the "updates" folder of the Lync package as "custom.msp".

Compressing the Lync Client

Using 7zip we will now compress the source folder.  Simply right click the folder that contains your install and select 7-Zip>Add to "(foldername).7z"

Create a second folder and add the resulting 7z file - this is the folder that will be deployed over to the clients machines.  For this example mine is called "Microsoft_Lync_2013_x86_01"

Add the 7za.exe command line tool you downloaded (you did download it right?)
Create a batch file called "TSINSTALL.bat".  In the batch file add the following lines:

md c:\lync2013x86
7za.exe x Microsoft_Lync_2013_x86_01.7z -oC:\lync2013x86
cd c:\lync2013x86
setup.exe

Continue to PART 2



Wednesday, 23 January 2013

Lenovo X1 Carbon PXE Boot Issues

I  was recently given the nice new shiny Lenovo X1 Carbon to play with and deploy our corporate Windows 7 image to it.  To maintain its slim physique it hasn't got a built in Ethernet adaptor and is supplied with a Lenovo USB 2.0 to Ethernet Adapter.  Obviously we now had to track down the driver to inject to our Boot Image.

Initially we used the Lenovo USB 2.0 Ethernet Adapter Driver 5.4.3.0 which PXE booted but then seemed to fail and hang once WinPE loaded up.

I then downloaded the Lenovo X1 Carbon SCCM Driver Pack which came with v5.12.4.0 which also seemed to give me problems.

Eventually I found that it was the manufacturers Vista driver that worked for me.

From the AXIS website you can download the AXIS AX88772B Vista Driver which worked a treat.  With the SSD this was a dream to image and was quite quick in comparison to others.

Hope this helps.

Chris.


Wednesday, 10 October 2012

Create a bootable USB pen for SCCM Windows 7 Build Deployment

If you are ever in a situation where deploying your OS by SCCM's more conventional methods (ie PXE or LAN based deployments) isn't feasable (bandwidth/no connectivity) then you can prepare a USB pen and deploy to machines via a USB boot.

I've found the SCCM built in method of making a USB pen to be quite unreliable so I opt for the manual method.

Just a few heads up first:

  • I'd recommend at least an 8GB drive but in reality your build (if corporate) will eventually exceed this.
  • The pen will be totally wiped clean - all data will be lost.
Step 1:  Preparing the USB pen

  1. Open command prompt
  2. Type diskpart and press enter
  3. Type list disk and press enter
  4. Find your disk in the list
  5. Type select disk * (* being your number)
  6. Type clean and press enter - you should see "DiskPart succeeded in cleaning the disk."
  7. Type create partition primary and press enter - you should see "DiskPart succeeded in creating the specified partition."
  8. Type select partition 1 and press enter - you should see "Partition 1 is now the selected partition." 
  9. Type active and press enter - you should see "DiskPart Marked the current partition as active."
  10. Type assign and press enter - you should see "DiskPart successfully assigned a drive letter ..."
  11. Type detail disk and press enter.  For this example we will work with a drive letter "U" for USB
  12. Type exit to leave the Diskpart command and return to a standard prompt
Step 2:  Formatting & Copying

We are still using a drive letter "U:" so we want to type:

format U: /fs:fat32 /q YOU WILL LOSE EVERYTHING ON THE PEN HERE

Enter a label for the drive - this is how it will show in "Computer"

I copy the files manually - it works - but if you want to do it "properly" use this command:

In command prompt navigate to the location of your build files - this is what would have been extracted from the ISO that was produced in SCCM when you "Created Removable Media" from the OSD task sequence - if you need a guide on this mail me or leave a comment...

Type xcopy \*.* /s/e/f \ 

With our extracted ISO in C:\Win7Build and our pen being U:\ This would look like:

Type xcopy c:\Win7Build\*.* /s/e/f U:\ 

Don't forget you may/will need to adjust the boot order in the BIOS to accommodate booting from USB - you can find a guide here: http://bit.ly/TvndIW





Monday, 8 October 2012

Java Deployment (x86)

I've spent many hours searching the net for a definitive guide on how to successfully deploy Java across a network and to newly deployed machines.

In this instance I'm trying to add Java to an Operating System Deployment using Microsoft SCCM with two particular settings automated into the deployment.

I want the automatic updates to be disabled as this is constantly screwing up our clinical systems that get delivered to the users desktop as an update of Java resets several settings we have to configure post install.

The other is the Proxy set to "Direct Connection" as again our clinical systems hate any interference from the Proxy settings.


I've decided to repost my steps here in hope that it will help a fellow tecchy one day:

  • Download your choice of Java - I'm using 1.6.0.31.
  • Run the.exe and run to C:\Users\\AppData\LocalLow\Sun\Java\jre1.6.0_31
  • Copy the Data1.cab and jre1.6.0_31 files out of there into a folder of their own.
  • I already have a working WIM image I captured last week and didn't want to go through another capture so using the DISM GUI tool  I mounted my WIM and added a folder structure and the deployment.properties file to: C:\Users\Default\AppData\LocalLow\Sun\Java\Deployment.  Other settings for the deployment.properties file are available here.
  • Within deployment.properties was the following - it's actually one I created by manually altering the settings from the Java control panel and capturing the file from C:\Users\[username]\AppData\LocalLow\Sun\Java\Deployment
#deployment.properties
#Tue Apr 13 13:59:54 BST 2010
deployment.version=6.0
deployment.proxy.type=0
deployment.javaws.autodownload=NEVER
deployment.javapi.cache.update=true
deployment.security.mixcode=DISABLE
deployment.browser.path=C\:\\Program Files\\Internet Explorer\\iexplore.exe
#Java Deployment jre's
#Tue Apr 13 13:59:54 BST 2010
deployment.javaws.jre.0.product=1.6.0_31
deployment.javaws.jre.0.registered=true
deployment.javaws.jre.0.osname=Windows
deployment.javaws.jre.0.platform=1.6
deployment.javaws.jre.0.path=C\:\\Program Files\\Java\\jre6\\bin\\javaw.exe
deployment.javaws.jre.0.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.0.enabled=true
deployment.javaws.jre.0.osarch=x86


  • I committed the changes to the Wim and uploaded it back to our deployment server :::EDIT::: DON'T FORGET TO UPDATE THE DISTRIBUTION POINT!!!
  • Created a package for Java 31
  • Used the command line for the package program: msiexec.exe /i jre1.6.0.31.msi /qn
  • Hey presto - I'm now getting a Java deployment that automatically uses the settings defined in the deployment.properties file I created! BOOM !!!

Tuesday, 25 September 2012

Turn on logging for MSI installs

If you ever install from MSI's (which I'm sure you do) it can be handy to turn on logging so you can see the outcome - particularly handy if the install is failing.

Use the following code after your package.MSI and then a log file will be generated at the location you choose:

msiexec /i Packagename.msi /l*v c:\logname.log

Thursday, 2 February 2012

This task sequence cannot be run because a package referenced by the task sequence could not be found.

If like me you have been bashing your head against many firewalls during Windows 7 OSD via SCCM you will probably sometime come across the error:

This task sequence cannot be run because a package referenced by the task sequence could not be found.

More annoyingly it doesn't reference the guilty package in the onscreen error.  After checking the many log files CCM generates I found within the RAM drive path: x:\windows\temp\SMSTSLog resides the relevent SMSTS.LOG file.

The full error I recieved was after selecting the relevant OSD TS; resolving polices and then BAM :

This task sequence cannot be run because a package referenced by the task sequence could not be found. For more information, please contact your system administrator or helpdesk operator.

I also noticed (and please use SMS Trace to view error logs):

Failed to find CCM_SoftwareDistribution object for AdvertID="xxx", PackageID="xxx", ProgramID="*"

I found it was a Lenovo Graphics Driver Package causing the issue; it appears SCCM has yet another little "quirk" where the hash isn't written sometimes upon creation of a package and the initial ditribution.  If the version number of the guilty package is "1" try right clicking on the DP of the package and select "Update Distribution Points".

After some time the Source Version will increment to "2" and the date will be current - give your OSD another try and then see if it works - if it fails - check the log file again as this time the guilty package may have changed and it may be a case of trawling through a few before you resolve the issue.

I hope this helps.

Many thanks to J over at ManagedUX for the pointer!