-
Posts
87 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Bendes
-
-
-
Are the Boundaries (where the Client resides) created and assigned to a Distribution Point?
-
KMS is your best friend: http://technet.microsoft.com/en-us/library/ff793434.aspx
-
Is your deployment based on Collection with Query rules? Is so, is your Collection refresh delay short enough?
-
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
-
You must achieve this from SCCM Management console:
-
No CAS needed. CAS is required to manage multiple Primary Site. Then you can add it to your existing Site infrastructure.
-
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
-
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...
-
-
To be sure, before the rollout, create a deployment that will delete the registry key.
-
-
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
-
Maybe in log files: "C:\Program Files\Microsoft Configuration Manager\Logs\smsbkup.log"
-
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).
-
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/
-
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) ?
-
so i put this command at the command line field? Yes
do i need to enclose with " "? No
-
Last idea :
C:\Windows\System32\cmd.exe /c batfile.cmd
-
- Your batfile.cmd is present at the root of your "source" package folder ?
- Are your sources replicated to your DP's ?
-
Have you tried the simpliest way without "cmd.exe" ?
batfile.cmd or batfile.bat
-
Try uninstalling/reinstalling SCCM Client
-
With the following Tool you can check and fix WMI errors (and a lot of other cool things) :
-
Your Admin Team shoudn't worry about it. A "System Management" Container is added under "System" Container and a small pieces of Classes/Attributes :
Happy New Year!! (2013)
in General Chat
Posted
Happy New Year 2014 to all !