Trend OfficeScan 10 causing Hash Mismatch Errors in SCCM 2007

For the last 2 years of my SCCM Career I've been blighted with issues concerning the above.  I've added exceptions to our Trend server, calls have been logged but I can never seem to get this sorted.

I find that if Trend is running the execmgr.log will sometimes show Hash Mismatch errors.  If I manually disable Trend (or better still remove it!!) - it works fine.

I've started adding a quick command to my Task Sequences and package deployments to temporarily disable OfficeScan while the deployment takes place and it works a charm!!

Simply add the following command lines before and after via Task Sequence or simply create a package with a batch file containing the following.

Before:

net stop tmlisten
net stop ntrtscan

After:

net start tmlisten
net start ntrtscan

Obviously this works manually too if you should ever need to disable Trend remotely...  Even if it has a password!!!!!!!! ;)

AppV Application Slow to open

I've recently sequenced a Pathology application that we use in the NHS that uses a Terminal Emulator to retrieve bloods direct from the Lab.

I had managed to sequence it fine but the package was taking an age to load up and sometimes timing out completely.

After looking at the SFTLOG (C:\ProgramData\Microsoft\Application Virtualization Client) I noticed an error: 4636126-0B01FD04-0000041E

As per AppV error format:

App-V Error 04-0000041E

Event:
Starting/Running the application
Error Message / Symptoms:
It took to long until the application was ready for interaction with the users.
The application shuts down after about 5 minutes
Potential Causes:
The application is a Java or DOS like application. App-V can not determine that the application is ready for User Input, because the app does not use default Windows Classes.
Potential Solutions:
In the OSD file, SUBSYSTEM VALUE has to be changed from "windows" to "console" (case sensitive).
If it is an 16-bit application, also the VM VALUE should be set from "Win32" to "Win16"
References:
Microsoft Knowledgebase Article: http://support.microsoft.com/kb/931112. This articles lists a set of potential causes, however the most common reason (SUBSYSTEM "windows") is not listed there.

Thanks to Falko at  Kirx.org for the above.

Once I'd made these changes I updated the package and viola, Bob's your aunties live-in lover!

Operating System Deployment with USB Dongles (Lenovo in my case)

With the advances in technology we have seen in recent years, devices have become smaller, thinner and lighter than ever before.

With this we are finding that some devices are loosing functionality - ie. Some devices are having ports omitted to retain their slender profile.

The Lenovo X1 Carbon adopted this approach and required a USB dongle which I posted about the pitfalls of PXE boot here: Lenovo X1 PXE Issues

I've seen an increase in the issues these dongles are causing us deployment techs, one of those being that each of these dongles have their own MAC address.  In true tech style when we see this new wizardry the first thing we say is "MINE"... Well actually the first thing we normally say is "Ooh Shiney" but then there's a Smeagle like "My Precious" when we claim the Shiney as our own.

I did this.  I had my very own dongle.  It worked great.  ONCE!  Every subsequent build failed.  I did a bit of research and found that it had it's own MAC that was registering in SCCM so I had to surrender my Shiney and give it on to the user.

I now use the supplied dongles for each build as it isn't worth the trouble but I have it on good authority that with the latest gen of Lenovo kit they are shipping certain models with on-board NICs (therefore unique MACs) and the dongle is purely a port extender utilising USB to present an Ethernet port.

If you have fallen prey to this (and insist on using one dongle to rule them all) you need to read my earlier post to search SCCM for machines by their MAC address.

Have fun...

DocN

iPhone Activation Error

So if you, like me have woken up on 6th October 2013 to find a nice little error on your crApple device asking you to "Activate" then you may want to find out how to fix it.

 

As the calendar rolls over to 6th Oct; Reports are coming in from all over the World of people with iOS7 beta6 being locked out of their phones due to the expiry of the test version of the nice shiney iOS7 being retired.

Blah blah blah I'm going to cut the crap and just get on with it as it's Sunday morning and I'm trying to enjoy my kids, a bacon butty & a cup of tea...

Get the stuff you need & back it up baby...

• Download the latest crapTunes or update from within crapTunes.
• Backup your crapPhone with crapTunes if you can (I couldn't).
• You can still access photos so if you need to, back them up too.
• Download the latest version of iOS 7.0.2 from one of these sources (not responsible for external content etc etc) then hold down on the option key (Mac) or the shift key (Windows) and click the “Check for Update” button in the Summary pane of crapTunes. Browse to the file you downloaded. (it will take an age!)
  

iPad2(Wi-Fi) (iPad2,1)	7.0.2 (11A501)
iPad2(AT&T) (iPad2,2)	7.0.2 (11A501)
iPad2(Verizon) (iPad2,3)	7.0.2 (11A501)
iPad2,4 (iPad2,4)	7.0.2 (11A501)
iPad2,5 (iPad2,5)	7.0.2 (11A501)
iPad2,6 (iPad2,6)	7.0.2 (11A501)
iPad2,7 (iPad2,7)	7.0.2 (11A501)
iPad3,1 (iPad3,1)	7.0.2 (11A501)
iPad3,2 (iPad3,2)	7.0.2 (11A501)
iPad3,3 (iPad3,3)	7.0.2 (11A501)
iPad3,4 (iPad3,4)	7.0.2 (11A501)
iPad3,5 (iPad3,5)	7.0.2 (11A501)
iPad3,6 (iPad3,6)	7.0.2 (11A501)
iPhone4 (iPhone3,1)	7.0.2 (11A501)
iPhone3,2 (iPhone3,2)	7.0.2 (11A501)
iPhone4(Verizon) (iPhone3,3)	7.0.2 (11A501)
iPhone4S (iPhone4,1)	7.0.2 (11A501)
iPhone5,1 (iPhone5,1)	7.0.2 (11A501)
iPhone5,2 (iPhone5,2)	7.0.2 (11A501)
iPhone5,3 (iPhone5,3)	7.0.2 (11A501)
iPhone5,4 (iPhone5,4)	7.0.2 (11A501)
iPhone6,1 (iPhone6,1)	7.0.2 (11A501)
iPhone6,2 (iPhone6,2)	7.0.2 (11A501)
iPodTouch(5G) (iPod5,1)	7.0.2 (11A501)

•  Choose the file and let it do it's thing.  Don't worry - you won't loose any data either!!!

BLOODY CRAPPLE!!!


DocN

There may be too many steps in the task sequence object.

So this was a new one on me.  Before you ask; no, we hadn't made any changes to our system - it just happened.  Yes - it just happened, just like I'm guessing has happened to you if you're reading this.

I fired up my SCCM console locally on my machine.  I went to edit a Task Sequence and then got this little gem:

 

Good one uh?  I then jumped on the server and tried the server console.  Still the same.

A bit of twitchy bum moments, log file seaching and a touch of Googling I found that this could be caused by MDT going; what we in the industry call; "Tits up".

Do you have MDT integrated into SCCM too?  You do?  Good - read on...

Try re-running the MDT integration as per the start menu folder location for MDT on your SCCM server and you should find things fine and dandy.

It didn't work?  Oh... Sorry - try this link here.

'Consumerization of IT' Taking Its Toll on IT Managers

http://www.cio.com/article/689944/_Consumerization_of_IT_Taking_Its_Toll_on_IT_Managers

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