Jump to content


Bendes

Established Members
  • Posts

    87
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Bendes

  1. Are the Boundaries (where the Client resides) created and assigned to a Distribution Point?
  2. KMS is your best friend: http://technet.microsoft.com/en-us/library/ff793434.aspx
  3. Is your deployment based on Collection with Query rules? Is so, is your Collection refresh delay short enough?
  4. The principe is simple: 1. Configure your image (syspreped) 2. Boot on WinPE (via Network Boot or USB Boot) 3. Map a network drive in command line (NET USE) where ADK Tools are available 4. Use IMAGEX to capture your image to the mapped drive
  5. You must achieve this from SCCM Management console: http://blogs.msdn.com/b/scstr/archive/2012/05/31/how_2d00_to_2d00_install_2d00_and_2d00_configure_2d00_the_2d00_dp_2d00_site_2d00_role_2d00_on_2d00_a_2d00_site_2d00_system_2d00_server.aspx
  6. No CAS needed. CAS is required to manage multiple Primary Site. Then you can add it to your existing Site infrastructure.
  7. Keep the EXE in your package and change your BAT as follow : REM MD C:\Temp COPY %~dp0Install.exe C:\Temp\Install.exe C:\Temp\Install.exe
  8. It's a common MSI error. If there is no log fille created, I think a prerequisite is missing to install LightRoom. Maybe check by starting it manually...
  9. Have a look at "Unattend.xml" creation : http://www.windows-noob.com/forums/index.php?/topic/3251-customising-windows-7-deployments-part-4/ http://www.windows-noob.com/forums/index.php?/topic/7975-unattendxml-english-uilanguage-with-other-language-keyboard/?hl=keyboard
  10. To be sure, before the rollout, create a deployment that will delete the registry key.
  11. Maybe it will help : http://www.sccm.biz/2013/05/how-to-boost-up-pxe-tftp-boot-speed.html
  12. Disabling the default Administrator (a ramdom password is then genrated) is builtin in Task Sequence : To create a new one, just create an Unattended.xml with WSIM Tool
  13. Maybe in log files: "C:\Program Files\Microsoft Configuration Manager\Logs\smsbkup.log"
  14. If User's file are saved on a Migration Point or a Network Share, just completely recreate your partioning as you wish (without the step of deleting/extending partitions).
  15. Try specifying in your USMT XML configuration to retrieve all files on D:\*.* and restore them back to a new location (C:\Old_D for example) A simple How-To: http://www.petervanderwoude.nl/post/some-basic-usmt-4-0-actions-explained/
  16. It's must be as simple as you say... Have you check the log files on your client C:\Windows\CCM\Logs (sort it by last modification) ?
  17. so i put this command at the command line field? Yes do i need to enclose with " "? No
  18. Last idea : C:\Windows\System32\cmd.exe /c batfile.cmd
  19. - Your batfile.cmd is present at the root of your "source" package folder ? - Are your sources replicated to your DP's ?
  20. Have you tried the simpliest way without "cmd.exe" ? batfile.cmd or batfile.bat
  21. With the following Tool you can check and fix WMI errors (and a lot of other cool things) : http://sccmcat.codeplex.com/
  22. Your Admin Team shoudn't worry about it. A "System Management" Container is added under "System" Container and a small pieces of Classes/Attributes : http://blogs.technet.com/b/configurationmgr/archive/2012/10/30/extending-the-schema-in-system-center-2012-configuration-manager.aspx
×
×
  • Create New...