Jump to content


JustinL

Established Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

2 Neutral

About JustinL

  • Rank
    Newbie
  1. Hi All, Wondering how others are forcing existing Exchange ActiveSync users to enroll in Intune. I've setup Intune integrated into our SCCM Current Branch (1602) environment and configured the Exchange Server Connector to sync devices from our On-Premise Exchange 2013 environment. All EAS devices are syncing into SCCM and I've successfully deployed Exchange On-Prem Conditional Access to a targeted user collection. For users in the targeted collection that have devices connecting to EAS via the native iOS or Android mail client things seem to work as expected. These users receive the CA email notification which provides instruction on how to enroll. Once they enroll, their device is then able to resume using EAS to send/receive email. This all works great. Here is where I'm running into an issue. We have a high percentage of users who are using the Outlook mobile app for both iOS and Android instead of the native mail client on their devices to connect to Exchange. The Exchange connector is syncing these devices into SCCM. They show up as Name=Username_Outlook and Device Type=Outlook. However users with an "Outlook" device are some how not being effected by the CA policy that is being deployed to them. Because of this I am not able to force their devices to enroll in Intune. So with all of that background can anyone tell me how I can deploy CA to users with devices using the Outlook App and force them to enroll their devices? I have found some documentation on deploying CA for Outlook mobile but it all seems to be related to 0365 and Exchange Online policy settings. We are not running 0365 and do not have a cloud based Exchange, everything is on-prem. Thanks in advanced for any help on this. Justin
  2. Hello, A while back I installed the IBM Deployment Pack to see what it had to offer in terms of OSD for our IBM servers. At the end of the 90 day trial I ended up uninstalling it. After the uninstall however it seemed to leave traces all over the console. Most I've been able to clean up except for the Add menu in task sequence editor (screenshot attached). Does anyone know of a way to remove these items from the menu? Thanks!
  3. I ended up running in to some issues with my previous solution so I wanted to post an updated solution that has been working. I went back to Technet and started researching the TS built-in variables and came across the SMSTSLocalDataDrive variable. From Technet: SMSTSLocalDataDrive Specifies where temporary files are stored on the destination computer while the task sequence is running. This variable must be set before the task sequence starts, such as by setting a collection variable. Once the task sequence starts, Configuration Manager defines the _SMSTSMDataPath variable once the Task Sequence starts. Does exactly what I was looking for! I created a collection variable for SMSTSLocalDataDrive and set it to C: on my OSD collections and voila the the _SMSTaskSequence folder now defaults to C: no matter what. Justin
  4. Thanks for the replies Peter. I was able to finally get this working with a little different method. In my Format & Partition step on the second partition I checked the box "Do not assign a drive letter to this partition". The task sequence still creates the partition but nothing can run from it because it has no letter assigned. With this in place the _SMSTaskSequence folder now defaults to C:\. I then added the step to run the diskpart script back into the task sequence to run right after Windows boots. The script successfully reassigns the ROM Drive to D: and assigns E: to the second partition. Justin
  5. Hello, Since moving to CM2012 I’ve been struggling to get my diskpart script that I used in CM2007 to work. The obvious difference between the two is that in my 2007 environment was set to access content directly from the DP and in 2012 I’m trying to stick with the default of download content locally. Here is my senario. The workstations have 1 disk with two partitions C: OSDisk D: Data Partiton E: ROM Drive Because of some custom software we run I need the data partition (D:) reassigned to (E:) then in turn the ROM Drive (E:) reassigned to (D:). to accomplish this I run the following run cmd line from my diskpart package diskpart.exe /s diskpart.txt diskpart.txt looks like this: select volume E assign letter J select volume D assign letter E select volume J assign letter D rescan exit This was very straight forward in CM2007 when accessing content from the DP but has become troublesome in 2012 because of the fact that the content needed to run the diskpart script in cached locally in the D:_SMSTaskSequence folder. The script itself runs fine until D: is reassigned to E: and the TS cant find the file anymore and bombs. I know i can always go through and set the packages and the deployment to run from the DP but I’d really like to try and stick with the recommended setting of download locally unless there is no other option. From what I understand the _SMSTaskFolder is defaulted to the drive with the most space. Is there a way that i can hard set the folder to C: instead? This seems like it should be a very simple step but I’ve been struggling with it for a week now. Any ideas on how to get the accomplished successfully would be appreciated. Thanks, Justin
  6. I was actually able to get this working late last night. I decided to pull all the updates from the deployment and try just one security update. With just the one updated in the deployment it installed. So it appears that there was a bad or unsupported update in the bunch. This morning I've been slowly adding updates back in to the deploy a few at a time to try and determine what bad one(s). I'd consider this issue resolved. Thanks to all who stopped in to take a look. Justin
  7. Hi everyone, I originally posted this over at myitforum but that I'd post here as well. A little background. I started out by migrating .wim's and task sequences from our 2007 environment but got all sorts of errors when adding "install applications" steps to these migrated task sequences. After fighting that for a few days I decided to scrap that and create some new reference .wim's and task sequences. I've got an MDT build and capture task sequence built and it completes successfully except for the fact that it does not install the software updates. I have the Updates deployed to the same collection as the build and captures TS and I have the SMSMP=servername in the "Setup Windows and ConfigMgr" step. I've reviewed the smsts.log (attached) and it appears that the TS sees the updates but does not install them saying "No Updates need to be installed on the machine" then completes the action and moves on to finish the TS. Funny thing is as soon as the machine finishes and reboots I log in and get a popup that updates are available. So the deployment to the collection is obviously working but i need help determining why the TS thinks that no updates need to be installed when there are clearly updates available. Thanks, Justin smsts.txt
×
×
  • Create New...