Jump to content


loewie1984

Established Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by loewie1984

  1. No need to disclose anything just be warned that LTSB cannot be used for regular computers. So as long as your company is aware of that it's ok. What happens when you create a reference image without languagepack and do not speficy any language properties in your cs.ini?
  2. First of all what is your use for LTSB? Are you deploying kiosks, bank terminals or POS systems than ok, if not DO NOT USE LTSB. Second, did you download your ISO from the myvisualstudio downloads section or somewhere else? You will need to check your unattend.xml and then especially the OOBE section in the XML file. It needs to be something like this: <HideEULAPage>true</HideEULAPage> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>1</ProtectYourPC> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideLocalAccountScreen>true</HideLocalAccountScreen> Cheers! Rens
  3. Sure no problem, and make sure you have downloaded and extracted the service packs of Office 2010 and put them in the .\updates folder in the root of your Office 2010 directory. Will make patching much faster because of the updates already present in the SP's. Use <sp_file>.exe /extract:<folder>
  4. I'd say not, as long as you initiate the Office 2010 Rearm vbs, which is enabled by default in MDT when you are doing a sysprep. Look it up in the scripts. LTISysprep.wsf: '//---------------------------------------------------------------------------- '// Rearm Office 2010 if it is present '//---------------------------------------------------------------------------- If not UCase(oEnvironment.Item("SkipRearm")) = "YES" then For each sOSPPPath in Array(oEnvironment.Substitute("%ProgramFiles%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"), oEnvironment.Substitute("%ProgramFiles(x86)%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE")) If oFSO.FileExists(sOSPPPath) then oLogging.CreateEntry "Re-arming Office 2010 activation", LogTypeInfo iRetVal = oUtility.RunWithConsoleLogging("""" & sOSPPPath & """") If iRetVal = 0 then oLogging.CreateEntry "Re-armed Office 2010 successfully.", LogTypeInfo Else oLogging.CreateEntry "Unexpected return code while re-arming Office 2010, RC = " & iRetVal, LogTypeWarning End if End if Next Else oLogging.CreateEntry "Re-arming skipped by user request.", LogTypeInfo End if Cheers! Rens
  5. Hi, Do you want to make any modifications to the installation or just want to use the original install.wim? Because that is located on X:\Sources on your Windows ISO or DVD Cheers! Rens
  6. Hello Luca, Indeed, setup.exe /download download's the files you want to download in relation to your Office 365 subscription. You can automatically generate a download and installation xml file through this generator: https://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html Then this will download the files, and you can use a different XML file as I've shown in my articles to actually install the Office-Click-to-Run installation. Cheers! Rens
  7. Luca, Skype for Business is part of an Office 365 plan. See these articles I've written on how to deploy Office 365 1. http://renshollanders.nl/2014/02/office-365-automatic-deployment-of-office-365-with-mdt/ 2. http://renshollanders.nl/2015/08/office-365-updated-deployment-guide/ 3. http://renshollanders.nl/2015/10/office-365-get-office-365-wave-2016-now/ Be sure to read them in this order, because some information is superseeded by my latest articles. Cheers! Rens
  8. Have a look over here, I've written an article that helps you to do just that: http://renshollanders.nl/2013/02/mdt-2012-settings-for-fully-automated-lti-deployment-part-ii-customsettings-ini/ Also see this website for reference: http://systemscenter.ru/mdt2012.en/propertydefinition.htm The cool thing is people start googling and open threads rightaway before even reading the help file, the second link is just that! An online version of the help file / articles present in MDT Cheers! Rens
  9. Hi, have a look here: https://social.technet.microsoft.com/Forums/windows/en-US/58c49d17-651f-46e7-aa61-db92bedfe0dd/disable-ipv6 It's all about these three command lines: netsh interface teredo set state disable netsh interface 6to4 set state disabled netsh interface isatap set state disabled Cheers! Rens
  10. Did you install or slipstream a language pack during OSD before .NET framework? If so, change the order into .NET first, language pack second! Cheers! Rens
  11. You can place the following information into your customsettings.ini for automatic joining of the domain: MachineObjectOU=OU=Computers,OU=Laptops,DC=contoso,DC=local NetworkLocation=Work JoinDomain=contoso DomainAdmin=srv-rollout DomainAdminDomain=contoso DomainAdminPassword=P@55w0rd Or store the same information in individual task sequence variables in your task sequence, so only desired task sequences can hold the domain join information. Cheers! Rens
  12. Hi this is perfectly possible using a diskpart script and refresh scenario during MDT or just only the "Install Operating System" step in ConfigMgr. Basically it should exist out of the following options / commandlines that are written in a little text file called "Format-C-Only" (or something like that): SELECT disk 0 SELECT partition 1 FORMAT FS=NTFS LABEL="Windows" QUICK OVERRIDE ASSIGN ACTIVE EXIT Then it can be called from within your task sequence like so: DISKPART /S X:\Format-C-Only.txt Note that the OVERRIDE switch is important, when for instance you are using disks that are bitlockerd, and in any other case it doesn't hurt to use it too. If you want to put in other options, please visit this link for other DISKPART command line features: https://technet.microsoft.com/en-us/library/cc766465(v=ws.10).aspx Lastly if you want to do a check if a computer has been partitioned with the scheme a previous time, there are conditions to set in both MDT and SCCM that do a check for a file, timestamp, presence of a file, or something like that. I always like to tattoo my machine with information that I pritty much echo from my task sequence variables into a little text file called "DeploymentInfo", which I use as a condition to check if the file exists, and if it exists, I assume the machine has been deployed a previous time. Cheers! Rens
  13. Hi, depending on which tool you are using, this may be an example which will help you get further: http://www.deploymentresearch.com/Research/tabid/62/EntryId/103/Generate-computer-names-in-MDT-2012-2013-based-on-prefix-and-a-sequence-number.aspx It was already possible to store computernames in a database with MDT, just as it is with SCCM. But this blogpost explains how to achieve hostnames that are automatically followed-up by the previous/last given hostname. Cheers!
  14. Hi, This is what you are looking for: http://flylib.com/books/en/2.568.1.35/1/ From that post, use the following: SELECT * FROM RegistryValueChangeEvent WHERE Hive = 'HKEY_LOCAL_MACHINE' AND KeyPath = 'SOFTWARE\\MICROSOFT\\WBEM\\CIMOM' AND ValueName = 'Backup Interval Threshold' Cheers Rens!
×
×
  • 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.