Peter33

Is that really an PXE error or just your monitor? I got trouble sometimes on lenovo machines which are connected via display port to the monitor. They don't like the low resolution switching and just go to sleep.

Ok, here is an actually working script $file = [Environment]::GetEnvironmentVariable("USERPROFILE") + "mypath\myfile" if (Test-Path $file ) {return $true}

Hi Luke, the bypass switch is just telling powershell to ignore the local policy and to run the script in any case. Also make sure that the Network Access Account has access to the share you are referring to in your command line. Linking it directly to the D$ is probably not a good idea. Also pointing to the local drive of the server "D:\..." will not work. If you run an external command inside of your script which requires administrative rights, make sure that you start them with the "-nonewwindow" switch. Otherwise it will trigger the UAC and your script will just hang until timeout.

Well, you could still try a custom script detection with powershell $file=[Environment]::GetEnvironmentVariable("USERPROFILE") + "\mypath\myfile" if(Get-Item -Path $file -ErrorAction SilentlyContinue){ [Environment]::Exit(0) } Else { [Environment]::Exit(1) }

What does your detection rule look like? If the deployment type runs in user context you should have no problems with the detection rule to catch user settings. For pathes you have to use variables though, like %appdata% %userprofile%. For the registry the build in path for current user works just fine.

I don't see why you are using the %msgsys variable at all. You can simply use %computername% inside of your script. Also, create a package for your script and don't run it from the distribution point. Always run powershell comand lines with the switch "-executionpolicy bypass".

SCCM 2012 is creating an "unknown" object for every device that boots via PXE and adds it to the collection "all desktop and server clients". Just delete this "unknown" entry and you will be able to PXE boot again.

Check the User Experience section of your ADR for the deadline behavior and activate the software installation checkbox.

You will need to extend your hardware inventory to the WMI clas win32_pnpentity. But this would feed a lot of data to your database. You also could extend the inventory to the registry key representing the device. A different approach would be to use the application model and set a new requirement through a WMI query and deploy the app to all clients.

Just right click the driver and add it to your boot wim. Chose to update the distribution points when finished. That's it. SCCM will mount the wim in the background and add the driver with dism.

You could use a script wrapper. Here is how you can do it in powershell. $Path = Split-Path $script:MyInvocation.MyCommand.Path Set-Location $Path $ExitCode = 0 $myargs = "/s /f1""" + $Path + "\Setup.iss""" $ExitCode = (Start-Process -FilePath "Setup.exe" -ArgumentList $myargs -Wait -Passthru -NoNewWindow -ErrorAction SilentlyContinue).ExitCode [Environment]::Exit($ExitCode)

I don't go with add remove programs usually, because not all products will register there.

Yes sorry, there is a small section company and products hat covers the installed software inventory. Installed software must be activated though for inventoring first. It's not a default inventory setting. Im used to create my own reports though for specific products for our license staff.

Just create a custom report which qeuries the "Installed Software" section for the product code or product name. The standard reports in SCCM are made for software distribution and not for inventory.

No, you don't need to create a new PE. If you are going to image the new model you have probably already imported the drivers and created a new driver package for it. Just pick the appropriate network and storage driver from this package and add them to the PE file. SCCM will reacreate the PE for you.

You need to distribute the content to at least one distribution point before you can use the image for a task sequence media.

Without having tested the Application Catalog with Windows 8 now i would guess this is a problem with the enhanced protected mode of Internet Explorer 10. Disable it in the advanced properties of the internet settings on your client and see if it works.

If you got trouble with PXE it's mostly because of BITS. To fix it, disable the PXE on your distribution point. Make sure that you remove the checkmarks of the 3 checkboxes before you uncheck the "enable PXE" box (there is a bug in SCCM 2012). When being asked if you want to remove WDS too, chose Yes. After doing this open your server manager and remove the BITS feature. Then reboot the server (you don't need to remove WDS manually through the server manager). When the server is up again enable BITS in the server manager. Open the SCCM console and anable PXE. Wait a minute and reboot the server again. That should fix the problem.

That's a Firewall problem. You need to enable some Inbound Rules.

Here you go. It's called Offline Servicing. As additional comment. Offline Servicing only works for the first index of the image file, so for combined images with multiple Base images only the first one will be patched. I used a combined image in SCCM 2007 for single task sequence USB thumb drive depoyments. This will not work in 2012 anymore, at least for the Offline Servicing part.

My suggestion for you is to use the Microsoft Deployment Toolkit. Run the Gather command from the MDT which will give you a variable "DefaultGateway001", which you can use. You can also apply the site settings through the customsettings.ini of the MDT. This way you don't need to define a single task sequence step for every location. The WMI Class you are trying to query is probably not available during the PE phase.

You can deploy both sequences with the x86 boot image. The x64 image is only needed for the capturing of x64 systems.

Rather group your software installation steps and run a WMI query to check if the software is already installed, so they will be be only executed if the condition is FALSE. Anyways there are several scripts around to force a hardware inventory (software is getting inventoried with hardware inventory). Here is one of them.

The Setup.iss is just an answer file for the Setup which holds the step by step information about every input you performed during the capture process of the setup "setup.exe /r". This file is essential for silent installations. The file itself will be held in the package location on the client (SCCM client cache). No user has access to this folder (only admins). Also, there is no User input available during a silent setup based on the answer file. Even if someone would modify the file in the cache, the SCCM client would notice the difference and redownload the sources before the next execution of the deployment.

Because SCCM would interprete the whole line as executable path oterwise. This way the system can make a difference between the executable and arguments. What happens if you name the answerfile just Setup.iss and the run a simple CiscoEmailSecurity-7-2-0-039.exe /s ?