Jump to content


sysadmin101

Established Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    1

sysadmin101 last won the day on June 14 2016

sysadmin101 had the most liked content!

Community Reputation

1 Neutral

About sysadmin101

  • Rank
    Member

Profile Information

  • Gender
    Male
  1. Hello! Can someone advise me how can I configure MDT Deployment Workbench Monitoring for SCCM MDT Task Sequences? I went through the guides online, and they ask to create a new Deployment Share in MDT - but I already have an existing SCCM MDT Task Sequence and content, so I won't be using the MDT's Deployment Share. Nonetheless, I created a Deployment Share in MDT, and also enabled Monitoring, however - There is no option to select 'what' is monitored (which logs folder/SCCM task sequence) Nothing appears even after completing some task sequences Can it even monitor SCCM MDT task sequences? Or it can only work with MDT task sequences (no SCCM)?
  2. if I create a standalone task sequence media, the retrieving policy step takes mere seconds! I don't understand why if booting from PXE, it's so much slower. I'm almost tempted to create a standalone WDS to let my clients PXE boot the standalone media (and from there proceed with the task sequence).
  3. how do you troubleshoot a slow PXE OS deployment? My deployment is slow in 2 areas - Retrieving policy for computer at the beginning; it takes 5-10 minutes! I only have 1 task sequence! My boundary groups are configured, I believe, optimally I used subnets for associating clients to boundary groups The client is on a subnet that is associated with only 1 boundary group The configured boundary group has no fallback at all (just to eliminate possible issues with client falling back improperly, causing slow deployment) Resolving task sequence dependencies Again, this takes 5-10 minutes before the task sequence actually begins Why does the above steps take so long? How can I go about troubleshooting this? Any help is much appreciated!
  4. Hi, If I apply drivers from a package during a OS deployment task sequence, will SCCM install all drivers within the package, even if the devices are not connected to the PC, or SCCM will only install drivers from the package, for the devices that are connected to the PC during the installation?
  5. Hi! I am deploying W10 1809 using SCCM + MDT UDI. However, my TS is a little different. I want to run UDi Wizard before any disks are formatted For that, Toolkit package must be used first This is only possible if there is a formatted disk, or if TS runs the files directly from the share (which I did not enable) Instead, what I did was Add the Toolkit files directly to the Boot Image (so that I can run it, without formatting the disk, and without running directly from a network share) Run ZTISCCM.wsf as the first task in the TS (I assume this is same as 'using toolkit package') Run cscript UDIWizard.wsf (UILanguage is defined here) Define a few more TS variables using additional tasks Install OS Apply Windows and Network settings Install Language Packs Everything works well, no errors whatsoever. However, when the task sequence is completed, Windows is stuck in the spinning dots screen for over 30mins! I've googled endlessly and despite the well known workaround of configured unattend.xml with the following settings: <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <VMModeOptimizations> <SkipNotifyUILanguageChange>true</SkipNotifyUILanguageChange> </VMModeOptimizations> <HideEULAPage>true</HideEULAPage> <HideLocalAccountScreen>true</HideLocalAccountScreen> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo> </OOBE> I still get the stupid spinning dots screen running for over 30 mins. Can anyone help me? I am totally at my wits end....
  6. Hi! I have OS deployment working in SCCM via WDS-enabled DPs. So I decided to try the new WDS-less option, but it seems broken? I tried with 2 different DPs, and I get errors such as: Client Boot TS reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> SCCMPXE 10/1/2018 6:35:28 PM 7696 (0x1E10) PXE: 00:1A:4A:16:01:F3: No Task Sequence deployments. SCCMPXE 10/1/2018 6:35:28 PM 7696 (0x1E10) PXE: 00:1A:4A:16:01:F3: Sending abort. SCCMPXE 10/1/2018 6:35:28 PM 7696 (0x1E10) But 2046820352 is 'x64 unknown PC' and I've certainly advertised the task sequence to the 'unknown device' collection for PXE/Media clients. (basically I took existing WDS-enabled DPS and checked the 'Enable a PXE responder without WDS' option) What gives?
  7. Hi Folks, Hope all is well! I'm trying to enable IPv6 PXE boot on my DP, but the checkbox simply isn't there. I'm on 1806, and I've already selected 'enable PXE responder without WDS'. My DP does not have an IPV6 address assigned at the moment (although IPv6 is certainly enabled at the NIC/OS) - does that need to be configured first? p.s. my clients will be PXE booting from a different subnet. Currently I use IP helpers to point the clients to the PXE server. The IP helpers are IPv4; I assume I will need to create IPv6 helpers as well? Thanks!
  8. I set the unattend.xml file specified in 'Apply Operating System Image' step with hard-coded Russian locale: <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UILanguageFallback>en-US</UILanguageFallback> <InputLocale>ru-RU;0419:00000419;en-US;0409:00000409</InputLocale> <SystemLocale>ru-RU</SystemLocale> <UILanguage>ru-RU</UILanguage> <UserLocale>ru-RU</UserLocale> </component> I verified that it is indeed Russian during OS installation in WinPE, in the following file: C:\WINDOWS\panther\unattend\unattend.xml But when it comes to the installing language pack step, it keeps returning this FindFile: The file Packages.xml could not be found in any standard locations. Packages.xml not found. Creating Packages.xml Creating new Package: C:\_SMSTaskSequence\packages.xml Unable to find the Packages.xml file, assuming there are no packages to inject. Adding non-language pack entries to unattend.xml Adding language pack entries to unattend.xml No <servicing> node found, adding a new one. Nothing to save, exit. Language pack entries added to unattend.xml successfully About to run command: dism.exe /Image:C:\ /Apply-Unattend:"C:\WINDOWS\panther\unattend\unattend.xml" /ScratchDir:C:\_SMSTaskSequence\Scratch /LogPath:X:\WINDOWS\TEMP\SMSTSLog\ZTIPatches_DISM.log Instead of: Creating new Package: D:\_SMSTaskSequence\packages.xml About to run command: expand "D:\_SMSTaskSequence\Packages\PRI00037\ja-jp\Microsoft-Windows-Client-Language-Pack_x64_ja-jp.cab" -F:update.mum "D:\_SMSTaskSequence\ZTIPatches.tmp" Command has been started (process ID 756) ZTI Heartbeat: command has been running for 0 minutes (process ID 756) Return code from command = 0 Create Package Item : Microsoft-Windows-Client-LanguagePack-Package What is wrong? I'm losing all my hair over this I already specified UILanguage as RU-RU, why does the deployment ignore it and not try to install the Russian language pack?
  9. I have 2 identical task sequences to install Windows 10. One installs the Japanese language pack, the other installs the Russian language pack. The Japanese task sequence works perfectly - language pack is installed and Windows boots with all locale settings set as JA-JP. Logs show: Microsoft Deployment Toolkit version: 6.3.8443.1000 The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ZTIPatches Entered state. Deployment Method = SCCM Operating system being deployed requires amd64 updates. ConfigMgr patching state. Load XML.... FindFile: The file Packages.xml could not be found in any standard locations. Packages.xml not found. Creating Packages.xml Creating new Package: D:\_SMSTaskSequence\packages.xml About to run command: expand "D:\_SMSTaskSequence\Packages\PRI00037\ja-jp\Microsoft-Windows-Client-Language-Pack_x64_ja-jp.cab" -F:update.mum "D:\_SMSTaskSequence\ZTIPatches.tmp" Command has been started (process ID 756) ZTI Heartbeat: command has been running for 0 minutes (process ID 756) Return code from command = 0 Create Package Item : Microsoft-Windows-Client-LanguagePack-Package Adding non-language pack entries to unattend.xml Found 1 matching non-language pack entries. No <servicing> node found, adding a new one. Add package {475CAEC0-1C7A-454E-9AEE-70754ABE5C96} Copying package from D:\_SMSTaskSequence\Packages\PRI00037\ja-jp\Microsoft-Windows-Client-Language-Pack_x64_ja-jp.cab to D:\_SMSTaskSequence\Packages\Package_0001 Copy File: D:\_SMSTaskSequence\Packages\PRI00037\ja-jp\Microsoft-Windows-Client-Language-Pack_x64_ja-jp.cab to D:\_SMSTaskSequence\Packages\Package_0001\ Package {475CAEC0-1C7A-454E-9AEE-70754ABE5C96} added. Ready to Save! Adding language pack entries to unattend.xml An existing <servicing> node was found. Nothing to save, exit. Language pack entries added to unattend.xml successfully With the Russian task sequence, the language pack doesn't get install (and SCCM doesn't record the task sequence stop as having 'failed'). Logs (which has no errors) show: Microsoft Deployment Toolkit version: 6.3.8443.1000 The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ZTIPatches Entered state. Deployment Method = SCCM Operating system being deployed requires amd64 updates. ConfigMgr patching state. Load XML.... FindFile: The file Packages.xml could not be found in any standard locations. Packages.xml not found. Creating Packages.xml Creating new Package: C:\_SMSTaskSequence\packages.xml Unable to find the Packages.xml file, assuming there are no packages to inject. Adding non-language pack entries to unattend.xml Adding language pack entries to unattend.xml No <servicing> node found, adding a new one. Nothing to save, exit. Language pack entries added to unattend.xml successfully About to run command: dism.exe /Image:C:\ /Apply-Unattend:"C:\WINDOWS\panther\unattend\unattend.xml" /ScratchDir:C:\_SMSTaskSequence\Scratch /LogPath:X:\WINDOWS\TEMP\SMSTSLog\ZTIPatches_DISM.log Command has been started (process ID 592) ZTI Heartbeat: command has been running for 0 minutes (process ID 592) Console > Deployment Image Servicing and Management tool Console > Version: 10.0.14393.0 Console > Image Version: 10.0.14393.0 Console > The operation completed successfully. Process completed with exit code 0 Return code from command = 0 Remove Folder: C:\_SMSTaskSequence\Scratch ZTIPatches processing completed successfully. Command line cscript.exe C:\_SMSTaskSequence\WDPackage\Scripts\ZTIPatches.wsf returned 0 ReleaseSource() for C:\_SMSTaskSequence\Packages\PRI00039. reference count 1 for the source C:\_SMSTaskSequence\Packages\PRI00039 before releasing Released the resolved source C:\_SMSTaskSequence\Packages\PRI00039 Process completed with exit code 0 Somehow the Japanese task sequence runs in D:\ while the Russian task sequence runs in C:\ Both task sequences were created identical - with Windows installing to C:\ Even the same Sysprep file is used - just that JA-JP is replced with RU-RU. Yet the Russian task sequence has this log entry "Unable to find the Packages.xml file, assuming there are no packages to inject." and proceeds to create (what I assume is) an empty unattend.xml - as a result, it doesn't even try to install the language pack (because the unattend.xml file doesn't tell it to). P.S. I have another Korean task sequence (identical except for locale options) - this works perfectly fine as well What's so strange with Russian language packs?
  10. Hi! I have the following set up ADR - run every (Wednesday - i.e. N)software available time - 1 day after rule is run (Thur - i.e. N+1) installation deadline - 1 week after software available time (Thur - i.e. N+8)Deadline behavior - allow software update installation outside maintenance window; do not suppress system restart Maintenance Window - every Sunday (i.e. N+4) As you can see, software updates are made available on Thur - but the deadline is only 1 week later. Within this 1 week (Thur to next Thur), there is a maintenance window on Sunday (during which deadline has not yet reached). Will clients still install updates during this maintenance window, despite deadline not having reached yet? Also, from Thur-Thur (i.e. before deadline), will / can clients automatically install updates outside the maintenance window? I want clients to be able to install updates outside the maintenance window automatically do not reboot outside maintenance window during maintenance window - feel free to reboot/install So will / can clients install required software updates before deadline, outside of maintenance window? Alternatively, I could set deadline == software available date, and allow 'software update installation' outside of maintenance window (under deadline behavior) So clients definitely install required software updates outside the maintenance window. But once the software updates are installed, when will the client reboot? Immediately after software updates are installed? (since deadline has passed) Or during maintenance window only? If I want clients to reboot only during maintenance window (despite the deadline is over) - do I select 'suppress system restart' checkbox? But will this also suppress system restart during maintenance window? Thank you.
  11. Hi, I updated SCCM to CB and now face this error (well it might have been there even before then just that I didn't notice since I hardly used reports). Whenever I try to run a report, I run into this error about incorrect credentials (although the credentials were definitely input correctly during setup/installation). *It is definitely seen as a 'wrong password' because AD logs it as failed logon attempt under the account I tried updating the Reporting Services Point Account (under the Reporting Services Point role) but it doesn't help. The only workaround that I found is to go to the Report Manager (i.e. http://url_of_ssrs_servrer/Reports_sccm_DB_name) Then go to the Data Source If I click 'Test Connection', it immediately prompts me: Log on failed. Ensure the user name and password are correct. However, if I re-enter the password, and click 'Test Connect' (repeatedly) it works fine. If I click 'Apply' now, and quickly run a report, it works! But few seconds later, the reports fail to run again with the same error above. It's as if something is trying to override the credentials I keyed in - and it overrides using wrong credentials? if I refresh the Report Manager and try to 'Test Connection' now again, it again prompts me Log on failed. And I need to re-apply the workaround each and every time I want to run a report. Any ideas how do I fix this?
  12. Removing the MP role from all site servers and then re-adding it again solved both issues! Didn't need to run the script from scug.be / force a new content ID for all application deployments.
  13. Anyone has any insights? I do not have the OOB role installed at all - yet when I try to add Site System Roles, the OOB role is just not available (doesn't appear) for both CAS and PRI system servers
  14. Hi! I upgraded my environment from 1511 to 1602. After upgrading, application deployment during OS deployment is broken with these error: The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password. Supposedly there is a fix for that at http://scug.be/sccm/2013/01/27/configmgr-2012-sp1-powershell-script-to-repair-broken-applications-after-upgrading-them-from-rtm/but the site is down for me Also, after updating to 1602 - all my clients were no longer able to communicate with the server; 'days since communication' keeps increasing for *all* clients - even though they are all online. I tried pushing the latest client to all PCs - the latest client installed successfully - but all the clients still fail to communicate with the server, and now all have become unmanaged Anyone had similar problems with client losing communication after upgrading to 1602? What's the best way to fix? Thank you.
  15. I have a CAS+PRI SCCM environment. I'm trying to integrate Intel SCS into the environment to manage Intel AMT devices. When I go into 'add site system role' for either CAS or PRI server, the 'Out of band service point' role just doesn't appear as a role that can be installed. I do not already have this role installed for my environment. Am I missing something? How can I install 'Out of band service point' into my environment? Thank you.
×
×
  • Create New...