Rocket Man

Hi Hoping someone has an answer for this. I created a custom global condition that queries for a computer name.(this works) I have software that is required/available for certain machine names in a school, normally only 1 PC in a lab, approx 7 machines in total. When I create the deployment type and add the requirement I try the equals operator followed with values of PC1, PC2, PC3, PC4, PC5 etc.. (this does not work) I try the one of operator with the same values as above and this still does not work. At this stage I have tried every operator on the single deployment type such as begins with, one of, equals etc... with various values as above and also PC1:PC2:PC3:PC4...etc PC1;PC2;PC3;PC4..etc None of these work on the single deployment type. The only way I can get it to work is by having numerous deployment types like so: Deployment type1 My custom Global condition Operator equals value PC1 Deployment type2 My custom Global condition Operator equals value PC2 Deployment type3 My custom Global condition Operator equals value PC3 Deployment type4 My custom Global condition Operator equals value PC4 etc..... This is very time consuming as I have other software that meet the same criteria and also have alot more than 1 school. Is there a way to specify a multitude of computer names in the one deployment type(maybe my syntax is incorrect)?? i:e PC1, PC2, PC3, PC1:PC2:PC3 OR Is this not possible and I will have to do it the hard way? Thanks Rocket Man

Well I have never seen this before and it is strange to say the least. You say you are having trouble at a time in your TS when you are required to enter in a System Name...is this correct? At what stage in your TS is this a requirement? I have system prompt that requires no intervention of a mouse, the cursor is in the name field waiting for data, and the simple press of the return button after entering in the name continues the TS. Is this any good to you? (I know it does answer your question but it will get you out of a hole maybe!!) EDIT: this prompt is seated in the top corner of the imaging process also!! so no need to have to move any other boxes to see it!!

good stuff... you got it working via changing the reg key....but still bemused as to why it would'nt work without having to perform this reg entry. Do you have a proxy like geoffp mentioned? Just another thing I thought I'd mention......I never activate my custom image at this site prior to capturing it, it is captured in an unactivated state then the key is embedded into the OS during OSD and then my activate run commandline activates it automatically wihout failure. Did you activate your image prior to capturing it?

Well if it is a brand new HD you can take it that it is unknown to SCCM. Have you tried PXE booting after deploying this TS to the unknown computer collection? Otherwise you will have to log into the machine (if there is an OS on the unformatted HD??), put it on the domain, get the client onto it, isolate the system into a test collection and deploy your TS to this collection whilst the OS is live(staging).

The only other thing I can think of is maybe UAC has to be disabled that would be the only other TASK that I would have attached bar software etc.. that maybe making the difference(not sure though) You could add another run command line like so: reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f Attach this task before your windows activation. This turns off UAC to the lowest setting. If this does not work then add a restart computer TASK at the end of task sequence (this may be the solution) as my TASK Sequence starts the machine 2-3 times before it completes it.

Does the run command line task fail at OSD time? OR is it successful at OSD time? This task only takes anywhere between 10-15 seconds to run. Also, has your OS installed on the C drive?

If your policy is deployed to all systems then it is deploying to any system within your infrastructure that has a SCCM client installed on it, including servers!! (probably not a good idea as servers may require a different policy, there are built in policies for servers in SCCM) As Niall mentioned you define where clients get their updates from in the policy ,Microsoft updates, SCCM, WSUS etc..

Is it not a matter of injecting the winPE driver for you machine in question into the boot.wim to get it to boot? I have tried importing a boot.wim and get the same message as you, but as I mentioned above it is about getting the corect drivers injected into the boot.wims. Have you tried sourcing the NIC drivers for these models and inject them into the boot.wim?

SCCM 2012 SP1 (Configuration Manager is not mentioned) in this list!! http://technet.microsoft.com/en-US/library/jj628198.aspx

Sql 2012 SP1 is not a supported version (well it was not a week a go anyway!)

Yes this is another workaround!! But I have just found something out with either methods of shortcut deployments. If your machines are multi-user and user1 decides to delete any of the shortcuts from their desktop it will delete it from the public desktop also....so any user that logs into the machine will not have the shortcuts that were deleted by user1...damn this. I have since seen another work around which does work and prevents this from occurring but only if the users do not have local admin. They wont have permission to delete the shortcuts if they do not have local admin. The shortcuts deployed via batch or add files method does not matter any standard user can delete them which ends up deleting them for all users. At least with the OCT method as demonstrated in the link below will prevent a standard user from deleting them!! http://www.myangrydome.com/?p=1525 This does work but not for the Lync shortcut!!

Is your SQL reporting log increasing in size?? I had a similar problem where by my main drive was dramatically increasing in size every day for some reason. I pin pointed it to be the SQL reporting log. It was adding 3-4GB everyday(this site had approx 1500 machines). If this is the culprit then you will have to shrink the reporting DB and also change the recovery model to simple as it probably set to full mode at present!! Also 30GB for SQL, not sure about this? Would it not be better just to have a default C drive and also E drive with all installed on it?? Without sounding irrational but from a personal perspective it looks a bit messy with the current setup considering all these drives reside on the same server anyway?? Rocket Man

Another query: How do I send the same ADR to another collection. I have office 2013 updates that at the moment are deployed via ADR to my windows 7 collection, I also want to deploy this ADR to my windows8 collection. Do I have to create another ADR and point it to the office 2013 update source directory(that was created from my windows7 ADR) and then deploy this new ADR to the windows8 collection. Will this work, 2 ADRs' using the same source directory?? Thanks

This should work if you are using a MAK key. Are you placing the run command line after setup windows and configMgr task?? This is where it should be or anywhere after this if you are deploying apps/updates etc it can even go after these tasks but definitely not before setup windows and configMgr task!! Also the clients require internet access at time of this process...they do have internet access I gather? It works for me on the sites that I have volume key MAK licenses!! EDIT: As a test if it still does not work log into one of the imaged machines and run the command from a command prompt. If this still does not work then there is something wrong with your key that you have embedded into your task sequence. You have left the - between the serials of your key? i:e xxxx-xxxx-xxxx-xxxx and not xxxxxxxxxxxxxxx!

cscript //b c:\windows\system32\slmgr.vbs /ato will do it for you!!! Just add the above as a run commandline!!

I built approx 5 test labs with beta sp1 and had similar to you, some did it some did not. I thought it was a beta issue but obviously not. Thanks Microsoft for the early RTM release :angry:

If it has to be done during OSD then you could try devcon. This tool apparently has commandline fuctionality to disable devices. After having a quick look at it you could create a script that copies this executable to the system32 folder, then you could use a run commandline with the appropriate parameters to disable your device. Should work for you if this tool actually does what it says!! This Link has the parameters that may work in windows7 also. This Link has the devcon tool for windows 7..

Has anyone else experienced this irregular strange behaviour whilst PXE booting into WinPE. I make TS available and at the prompt I press f12 for network service boot, this should then automatically download the PXE file, but it does not. Instead it loads up another page requesting me to choose my boot file which is the x86 boot.wim. After I hit return it then continues to download the PXE file. This happens more often than not. It is very strange as I could test it on a physical machine and also on a VM and it may or may not do this. I have quite a few sites that are non SP1 and have never seen this behaviour ever. Anyone else have similar experiences? Thanks

Inject the winPE3.0 into your boot.wims and that should do the trick!! http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx

Just had a quick scan there myself and unable to find the exact source for this information.and as far as I remember it was short and sweet.the directions....but basically it is just a folder created called Sources(you can call it whatever you like)........I remember that everyone had read permissions to it......but to be honest...personally I just give my network access account full rights to it at the root and thats it.. Inside this folder you can have your sub folders, ie ADR update folders, driver packages, software etc......

WinPE is a bundled driver pack supplied from DELL(maybe other vendors) so that your boot images will boot any DELL machine whilst in winPE. (apparently) Just inject the package into your boot.wims...

Sometimes it is just hard trying to get a single driver that works, what I have found it does not matter which driver it actually uses to create the initial connection in winPE....the important factor is that the correct driver gets applied at driver package time to the device so that the OS and hardware communicate properly!!

Hi Just to let you know we are mostly DELL in our environment but there are some variants of HP laptops but just cant remember the exact models. The only drivers I have added to my boot images is the WinPE3.0 and this has booted up everything to date. You are sure your hardware is not faulty?

I never change the password or verify share validity for the NET Access account here:

Have you injected the winPE 4.0 into the boot images? It is available on the Dell website. http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx