Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About torbuck

  • Rank
  1. Greetings all I am wishing to create a Office 2019 package using the SCCM Office 365 Installer. Going through the menus in the Office Installer GUI, I have selected Office Professional Plus 2019 - Volume License as the product. Once I get to the Licensing and Activation part, I enable to automatically accept the EULA, select the KMS Client Key radio button option, and then under Product Activation, I am only presented with User Based activation. Since this will be used for clients that will not have a E3 or E5 Office 365 license, I wish to select Device Based activation, however that option is greyed out for some reason. Any idea why I cannot select Device Based activation through the Office 365 installer for Office 2019? If I can select Office Professional Plus 2019 - Volume License, I would assume that User Based Activation would be greyed out and not Device Based. I am using MS Endpoint Configuration Manager Version 1910 Thanks for any feedback on this!
  2. Greetings, I am in the process of creating a deployment application of Bluebeam Revu 2016 in System Center. Our organization wants to standardize all of our clients to to the lastest ver of Bluebeam. Currently we are a bit of a mishmash of versions, some a number of years old. The latest MSI of Bluebeam will uninstall previous versions up to Revu 2015, however there will be versions older that 2015 that we will want to uninstall when we upgrade our users. Bluebeam has provided a bat file that will remove all previous versions. I am trying to determine what is the best method to combine both the bat file to perform the removal and the SCCM application to install Bluebeam 2016. I was thinking that I could do this by creating a package for the removal script combining the package and the Bluebeam application as a task sequence. Unsure if this is the best method. If I go this route, I would likely need to add some sort of pause between the removal script and the Bluebeam install so that there is time for the removal process to complete before the Bluebeam 2016 application install kicks in. Any suggestions on the best practice on how to do this task would be welcomed. Regards, Torbuck
  3. Greetings Our organization is fairly new with SCCM and its imaging process. We come from an Altiris background, so a lot of the imaging process we are relearning. Our SCCM installation consultant left us with a imaging process where it basically takes the wim file right from the Windows install source, and then proceeds with a number of task sequences, molds the deployment to our preferred standard. We are interested in deploying our images in a different manner, where we install our Windows of choice in a Hyper-V VM, do whatever tweaks and updates that we want, and then use this as the basis of our image. I've seen a number of procedures that outline this method, however my question is, if we do this process, for that VM do we still follow the standard imaging process by putting that Windows VM into audit mode, as well as creating an unattend file using the Windows System Image Manager? If there is specific tweaks that we want for all windows profiles, how is this done through the capture media process? Also, we would like to use the VM to use as a reference image, so that we can periodically apply Windows updates, or make any necessary adjustments, and then use this VM to replace the deployed image on a ongoing basis. Let me know if this is possible, and if so, any direction on how this is done would be welcomed. Thank you
  • Create New...