vitalstatistix

You are better off using Exchange Transport rules rather than the content filter. set a rule that checks email for the particular words or phrases and deletes/rejects the message, and then restart the Exchange Transport service.

Thanks for getting back to me. even if I remove the variables and have the region settings manually input into the unattend.xml, such as: <InputLocale>EN-UK</InputLocale> It still doesn't apply them. I am deploying in a couple of weeks and dont really want to change all of my task sequences this late on!

I have integrated MDT but am using the standard SCCM task sequences for deployment. I have checked "use unattended sysprep answer .." I have created an unattend.xml file as follows: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>%OSDInputLocale%</InputLocale> <SystemLocale>%OSDSystemLocale%</SystemLocale> <UILanguage>%OSDUILanguage%</UILanguage> <UserLocale>%OSDUserLocale%</UserLocale> </component> </settings> <cpi:offlineImage cpi:source="catalog:e:/sources/install_windows 7 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> the variables are specified in the collection. the Task sequence runs correctly but the language and keyboard remain as en-US, and there is nothing in the logs that helps. Am I missing something?

I am also looking for a way of changing the default language of deployed operating systems. Or even changing the capture media to capture the language choice of the target OS (currently it changes the language back to en-US on capture). Any help would be most appreciated. thanks, Jake

Hi, many thanks for your reply. I have got my server configured as above, however that process requires the machine to be built and picking up a machine policy before the Endpoint client is installed. SCEP = System Centre Endpoint Protection Ideally I would like to have the Endpoint client installed as part of the deployment so that the machines are protected immediately. there must be an easy way to have the client install and update definitions before it completes the task sequence and allows users to begin using the machine?

Hi All, I am attempting to integrate SCEP installation during a deployment task sequence using RTM. Unlike the old FEP there is no deployment client package created at install, so at present the SCEP Client is installed after the task sequence has completed, and so leaves a vulnerable gap between deployment and SCEP installation upon policy retrieval. Does anyone have information on the best way of installing and updating the SCEP client during the task sequence? Thanks! Jake

Thanks for this, very useful!

Hi Anyweb, Would you happen to know the query statement for all FEP client workstations? I am trying to make a collection based on this. Many Thanks

Hi All, Anyweb you have set up a fantastic resource here and I hope I can in some way contribute to its sucess! I am currently developing a new Server 2008/Windows 7 network for the school, implemention will be in summer 2012. your SCCM guides have been great for testing and learning. I am hoping for a Q4 2011 release date for the final product or I am going to be pushing close to date of implementation! Regards, Jake