dalsoth

Think i was confusing the wake on lan for some reason with pxe. My bad. Will go back and test with non mandatory!! Thanks!

Thanks for the replies guys. On the link you just supplied he says "but make sure that the Task Sequence is not set to mandatory". This is to advertise a build task to unknown computers via pxe boot. So how can i NOT be making it mandatory as that is the only way you get the little tick box to allow the advertisement to apply to PXE boot. If i untick mandatory it greys out the pxe tickbox.

This is what i described already and does not work. I think someone said it is because the advertisement is mandatory. I get to the password bit and type that in and then it just auto goes through and runs the build without asking for the name.

Hi All I am trying to work my head around SCCM at the minute. So far I have a good grasp of the basics and have made a reference image and deployed it out. I would like some advice on how to deploy to unknown computers using R3 SCCM 2007. Usually we just use MDT and during the initial screen it prompts for a machine name as per our customsettings file. We then name it according to printed asset stickers we already have, so naming them as the bios machine asset number or some other sort of system is out the question. The best solution for us is to be able to name the machine with a prompt after its unboxed and fired off with a pxe build. Just like we do with MDT2012. The issue is that in SCCM 2007 there seems to be no way to do this. I have set up an image build task sequence as MANDATORY to the Unknown computers container. I was told that if i changed the collection variable on the unknown computers to OSDCOMPUTERNAME and left the other bits blank this would force a prompt for machine name before the task sequence started. This does not appear to happen. I think this does not happen because the task is mandatory (read that on some forum). If i take the mandatory bit away you can't tick the box to enable PXE for the sequence though which means i cant boot to it and start the build! ARGHH!! Does that make sense to you SCCM experts? I just want to boot to unknown computers using PXE without pre-populating any machine details and have it run a mandatory task to build the machine. I want it to prompt for the name. Obviously i will have a password set on the build so machines don't get wiped by mistake. That is all that is required for now Any help would be greatly appreciated. I know some people have scripts and whatnot that may do this but i just need one with instructions that actually works. Nothing has so far. Cheers!!

Hi All I am currently playing with Bitlocker here at work and have got all of the scripts and things done so that i can back up the information to AD. I admit though that I have not read up on this topic fully yet and wondered if i am going wrong somewhere. Currently i have it set up so that: 1) I can MDT a machine and choose it to set up BitLocker and this installs the recovery key to AD. 2) I also have tested running a command line managebde powershell command to force a machine that had been set up with BitLocker previously to also store its details in AD. Where I am struggling is this, what if i have 10 laptops in an OU with no Bitlocker enabled. How would i automate Bitlocker without rebuilding or manually starting Bitlocker? I have aplied the group policy that i used for the above which pulls the TPM stuff into AD and also sets up how to deal with the OS disk etc. What I cannot seem to do is to actually get it to TURN ON bitlocker itself and kick off the encryption. It would be nice to apply the Bitlocker GPO to a laptop OU and come back later and they are all encrypting (assuming TPM etc is on in the bios). At the moment i apply the policy to the OU and go back and Bitlocker is still off. Is this normal? Is there a way to do what i want to do? My current GPO settings are using the 2 options below and the options within each: Turn on TPM backup to Active Directory Domain Services Enabled Require TPM backup to AD DS Enabled If selected, cannot set or change TPM owner password if backup fails (recommended default). If not selected, can set or change TPM owner password even if backup fails. Backup is not automatically retried. Allow data recovery agent Enabled Configure user storage of BitLocker recovery information: Allow 48-digit recovery password Allow 256-bit recovery key Omit recovery options from the BitLocker setup wizard Disabled Save BitLocker recovery information to AD DS for operating system drives Enabled Configure storage of BitLocker recovery information to AD DS: Store recovery passwords and key packages Do not enable BitLocker until recovery information is stored to AD DS for operating system drives Enabled Any advice would be appreciated. Thanks!

I remember having this problem. I think you also need to make sure that you have the setting in WDS to make them press f12 and again to continue. I also remember perhaps in DHCP or elsewhere making sure they were pointed to pxeboot.n12 boot file so that it checked the architecture before continuing but this was a while ago and I am too hazy to recall much more. I believe you also need a valid x64 boot image on the server before it will work properly. This might also help: SCCM OSD – When to use an x86 or x64 Boot Image « SCCM FTW It will explain if you are unsure about what types of image can boot or build each other. http://www.digitalsupporttech.com/kb/932447/

Try gpresult on the machine to see what is applying perhaps. Maybe check that you have it applying to computers rather than users etc...

Disown her.

Couldn't give a monkeys about the politics. All of these middle eastern countries seem to want to blast themselves back into medieval times. Leave em to it. Bring on the racing!!

You can reset permissions etc in disk utility. Another utility that lets you do this and recover from other issues is Applejack AppleJack:Troubleshooting Tool for Macs | Free System Administration software downloads at SourceForge.net

cluberti.com » MDT 2010 and deployment from a USB key We have MDT on a usb disk and have no problems. Used the guide above.

Hi All With a few tips from some Edugeekers i managed to get my head around how to set up a couple of machines to enable me to remote in and control them using vPro KVM technology. We have purchased some Dell machines that use an additional AMD/ATI graphics card with a splitter for classrooms with projectors. The issue i noticed is that the vPro KVM remote control only seems to work with the onboard intel graphics. This is great if you are happy to use an analog VGA onboard graphic solution but rubbish if you tend to use an additional graphics card with a splitter. Anyone know a way around this or is the whole vPro remote control VNC to the computers a waste of time if you use any non intel embedded graphics card? I noticed this information on the following website that mentioned a possible way to get this to work. http://www.realvnc.com/products/viewerplus/ViewerPlusProcessors.pdf It mentions at the top of the document that your OEM may be able to provide a way to switch between the onboard graphics and the 3rd party card when you need to remote control the machine. Anyone know of this or use something like this? It's all well and good being able to get into settings of a machine remotely but the key to this for us is being able to get onto a machine during a bluescreen or similar when we are dealing with remote locations. It would be great to get past this hurdle. At the moment we are not using any of the enterprise stuff to set any of this up as we have only started to look at it and play with it. I was wondering if anyone had a decent method to get the MEBx settings out to machines without having to spend time physically tapping away at the computer. It is also slightly frustrating that to enable to KVM remote password you need to log into the machine via the intel console tools and set the password. It seems silly that we can't just do this at the vPro MEBx bios type screen when we do the other bits. At the moment, i am setting up the vPro MEBx settings on a machine then having to start it building via MDT and then scanning the subnet to pick it up on the AMT manageability commander tool to then set up the KVM password remotely. Not the best or convenient way to do things i am sure. Would appreciate any advice or help to tell me where we can do this better. Thanks!

Slysoft Virtual clonedrive the best of the ones i have seen above and tried.

I have a HP Micro server with the AMD processor myself and am using it with ESXi. Personally i have a DVD drive installed although some people use the CD bay for an additional disk. There is also a USB connector on the motherboard inside the case where you can actually run the ESXi system from instead of having to use a bit of space off one of your disks. Not tried running Win 2008 as I have a physical one running that at the moment but have tried Mac OSX which worked after some heavy tweaking although the performance was not great. Noticed that some guy had quite a few win 2008 virtual servers running off his and said they ran well. Think it was from comments on ebuyer. Some good links in the comments also for upgrading the ram and installing a second network card which i did. Great little system.

I believe you can just google: shockwave msi files Think you can get them at the 1st result. You are supposed to register with them etc but it is a pain to do it every time.