Jump to content


anyweb

Root Admin
  • Posts

    9244
  • Joined

  • Last visited

  • Days Won

    368

Everything posted by anyweb

  1. first things first do you have any details of what files were over written/infected ? and do you have valid virus free backups of the database and all other software
  2. take a look at this post for a list of log files and what they log, use CMTrace.exe to read your logs it's in the tools folder of your SCCM installation, https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/log-files CLIENT LOGS: all SCCM log files on the client are in C:\Windows\CCM\Logs SERVER LOGS: server side they'll be in \\server\sccm installation path\logs
  3. well what types of devices are they ?
  4. With Halloween only a few days away, this year Altaro gathered SysAdmins’ funniest and most horrifying stories into one eBook, especially for you. We all know that a SysAdmin’s job is no easy task and apart from constantly having systems to update, bugs to fix and users to please, SysAdmins encounter all sorts of situations throughout their careers. From tech situations to funny anecdotes, terrible mishaps or incidents with colleagues, this eBook includes real stories of what SysAdmins go through on a daily basis. The eBook is very easy to download as no registration is required. Click on Download and it’s yours. It includes more than 25 short stories but this one is our personal favourite
  5. you'll need to put together an extensive plan of actions to make sure you can cover everything, your best option is to go with choice number 1 and by the way there is no SCCM CB 1903, it's SCCM Current Branch version 1906 (currently). To upgrade, start by reading these points. https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager as you can see there is a lot to review and plan, and that's the first thing you need to do, so get too it and good luck. If you need some pointers I can include a rough draft of how we did it on one of our production upgrades cheers niall
  6. I've not tested it with MDT only, but you could and then provide feedback to us both MDT and SCCM use task sequences so in theory, it should work.
  7. did it download the file? if it did then look at this log file... $Parms = " /IAcceptLicenseTerms True /Quiet /Norestart /Log SQLServerReportingServiceslog.txt"
  8. perhaps as the task sequence itself can have steps which add/change those sections in the unattend.xml file, so again, look at what's in the specialize section and figure out which of those settings is causing it to fail, once you've identified it, then figure out what section of the task sequence is settings those values.
  9. @MagnumVP what's weird is the upgrade scenario, i have not tested migrating anything from 32 bit to 64bit
  10. in PowerShell, any line that begins with # is ignored. I.e. nothing will be executed.... the 4 lines you've quoted above won't do anything...
  11. Windows Server Update Services (WSUS) is needed for software updates synchronization and for the software updates applicability scan on clients. The WSUS server must be installed before you create the software update point role. The following versions of WSUS are supported for a software update point: source > https://docs.microsoft.com/en-us/sccm/sum/plan-design/prerequisites-for-software-updates
  12. I haven't tested that exact scenario so can't guarantee this will work but you could try this approach and see what happens https://www.niallbrady.com/2016/05/17/introducing-the-windows-10-uefi-bitlocker-frontend-for-system-center-configuration-manager-current-branch/
  13. hi then you are not following this guide. The error message above clearly tells you what to do to solve the problem. Add the site server's machine account to the local administrators group on the SQL server computer.
  14. I blogged about the subject some time ago, although my blog post was focused on workgroup computers, take a look it might give you some ideas
  15. hi Harley, that line is basically showing you that you can add Additional Attributes via PowerShell, you just need to define them, try it in a lab first and you'll see they get set correctly, then adjust for production use and do the same thing good luck ! cheers niall as regards part 8, that's all about time and things, right now i focus on work and 'releases' from Microsoft, when they release something that i should blog about, i do (for example the MBAM stuff in TP1909)
  16. how long it takes depends on what hardware you are running it on, using the latest and greatest with lots of ram and loads of CPU, maybe 30-45 minutes, using something old and lacking in resources, hours....
  17. yes i get that, but the error reveals the section that's causing your problem, and it's in the Specialize section of the unattend.xml, so some component in there is causing your issue, keep pulling bits out (either manually before it reboots into windows setup) or on the server itself and update the new xml to your dp's before testing again
  18. ok so here's the pass where it's failing, if you remove this section entirely -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Deployment"> -<RunSynchronous> -<RunSynchronousCommand> <Order>1</Order> <Description>disable user account page</Description> <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path> </RunSynchronousCommand> </RunSynchronous> </component> and then figure out why your product key is not being populated in your %OSDProductKey% variable then i think you'll make progress...
  19. if you just followed the guide things would work, but you have changed the SQL config and are wondering why things are now failing, post your sql config (ini) here so we can see how you configured it cheers niall
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.