Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

RhoSysAdmin's Achievements


Newbie (1/14)



  1. I realize no one has touched this discussion in years, but if you're still our there Rocket Man, I have a question about the above statement. What client setting equates to "custom software evaluation"? I assume "software deployment" is associated with the "software deployment" client setting. The article you referenced is great, albeit a little brief on the details. It's still a big help for me, having to solve this exact issue with our SCCM CB 2004 setup.
  2. We are testing deployment of applications that require administrator approval. I would like to enable the Service Desk to approve these requests. But I don't want to make them full blown admins, or even application administrators. What kind of custom (or built-in) security role do I need to create, and do I include the computer or user collections (or both) in the scope for this role? We're running SCCM current branch 1706.
  3. We have a working base image for Windows 10, and are able to deploy it using SCCM current branch and MDT 2013 (thanks largely to the guides on this web site). We're now want to start testing the enabling of BitLocker when we deploy new computers. We're already setup BitLocker and are saving recovery keys to AD. We're been doing manual setups of laptops up to this point. I see a "Enable BitLocker" (Run Command Line) task in the standard MDT task sequence that runs "%deployroot%\scripts\ZTIBde.wsf" if a task sequence variable exists. I don't know what this script is going to do. However if I Add the Disk > Enable BitLocker task in the TS by hand, I get something completely different. This task is preferable since it's clear when you edit the TS that you know what it's going to do. Does this task assume TPM is already enabled? Is there a step that can confirm TPM is enabled, and if not, enable it? What's the preferred way to enable BitLocker during image deployment? Is there documentation, or anywhere else, that can help us with this?
  4. We're new to BitLocker and SCCM. We've got Windows 10 deployment working with MDT 2013 and SCCM current branch. We'd like to add BitLocker to this setup, but the standard "Create Task Sequence" template for the MDT Task Sequence wizard doesn't present any BitLocker options that I can see. Is there easy to understand documentation out there on how to add the enabling of BitLocker to your SCCM/MDT OS deployment of Windows 10? Thanks!
  5. My mistake. I don't know how I missed it. It's on the H:\ for my server (which is where I should have started looking). I do have a follow up question. On our SCCM 2007 server, the WDS install created a SMSPXEIMAGES$ share that pointed to E:\RemoteInstall\SMSIMAGES. On the SCCM Current Branch server, no SMSPXEIMAGES$ was created. I'm wondering if that was b/c I enabled PXE for my SMSPKGH$ share (H:\SMSPKGH$). I have two DP choices in SCCM 2007 (\\sccm2007\smspxeimages$ and \\sccm2007). I'm guessing this is b/c in SCCM 2007, we configured the "ConfigMgr distribution point" and "ConfigMgr PXE services point" site system roles separately? We've always used the \\sccm2007\smspxeimages$ DP for boot images, and the other \\sccm2007 DP for software packages and OS images. In SCCM Current Branch, there's only the "Distribution point" site system role to configure - which has a "PXE" tab in the dialog box. So there's only the SMSPKGH$ file share - b/c I restrict where SCCM can create package source locations on the server (no_sms_on_drive.sms files in root of all other drives). I've confirmed my boot image has been distributed to my one DP location. Both our SCCM 2007 and "Current Branch" setups are single site servers. We have one location so all roles are installed to just the one server in both instances. Is there any need to create a SMSPXEIMAGES$ to point to H:\RemoteInstall\SMSImages? Are my guesses correct regarding the differences b/t SCCM 2007 and Current Branch?
  6. Can someone tell me how the actions in step #6 "install Windows Deployment Services files to C:\RemoteInstall"? I don't see how this is done. I've enabled PXE as instructed and the WDS service is installed and running. But I was never prompted to configure it when installing the Windows 10 ADK.
  7. Why when I look at any of my boundary groups am I not able to change the speed associated with the server? I don't have a "Connection" column when looking at the References tab of my boundary group properties. We're running Current Branch 1706. Thx.
  8. I don't think a guide will be necessary after all. I just tried it as you described and it works. It's as simple as could be. Thanks!!
  9. I saw your example, and I use that already. A guide specific to using collection variables in the Options tab of the task sequence step would be great, if only so I can make sure to get the syntax correct. Thanks!!
  10. I would like to create groups within my task sequence that match a different roles in our company. Ghese groups get multiple software installs that those who get the baseline do not need. I want to define a collection variable along the lines of OSDComputerName (a trick I learned on this site), give the variable(s) values of 1, or yes, for the group(s) the computer belongs to when the TS starts, and have the TS execute the group if the collection variable is set. Is this possible? Is there a better way to easily install optional applications from a single task sequence? I want to make this as friendly as possible for our desktop deploy group. Thanks!
  11. Problem turned out to be wrong nic driver (XP driver on SCCM 2007 SP2 boot image instead of Win 7 nic driver). This issue is solved. KH
  12. I'm trying to work through the XP build and capture tutorial with my SCCM 2007 R3 system. The first suspicious thing is that the workstation identifies it's architecture as x64 at the bios, but then it will load my boot image. I see the SCCM 2007 splash screen, but then after a minute it reboots. I thought it might be that it wasn't a bare metal workstation, so I wiped the existing volume on it, but that didn't make a difference. I enabled command support, but F8 doesn't get me a command prompt. I've updated the distribution point for my OS install image, and double checked my task sequence against the tutorial in this forum. I don't know where to look next. [update] I apparently didn't do a clean removal of WDS and PXE before. I've done it again and now when it boots, it still identifies itself as x64 architecture, and I can still hit F12 and it does load the boot image I chose, and I still see the SCCM splash screen. I can now hit F8 and get a command prompt, but I cannot find any log files to review. It still reboots w/o having partitioned the hard drive. Any advice is greatly appreciated!! KH
  13. Well, I have PXE boot working now. Of course I have another issue, which I'm posting in a separate thread. The answer for me came in removing and reinstalling WDS and PXE (ref : http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx). Thanks. KH
  14. I've been trying to work through the guides on this site and on TechNet to work through setting up OSD in my network. I have SCCM 2007 R3, on a single 2008 server for my network. We have one site, and only about 400 computers. I'm working through Deploying XP first (http://www.windows-noob.com/forums/index.php?/topic/569-how-can-i-deploy-windows-xp-sp3-using-sccm-2007-sp1-part-1/), b/c it seemed easier than starting with Windows 7. The guide is great, but I feel like I'm missing some configuration steps. It seems I found out in the middle that I needed WDS to support the PXE service point, which is fine. But now it seems I'm missing more details. I now find out that I need to add DHCP options to get my PXE clients to actually boot. I feel like I've started a novel in the middle. Can someone point me to the guides I should be starting with, as far as OSD goes? Thanks!! KH
  • Create New...