Jump to content


learningmode

Established Members
  • Posts

    42
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by learningmode

  1. Not in the Device Event logs itself. But I have read some where that if the existing devices were Azure AD joined already with the standard license, then you upgrade to the intune licenses... The existing devices will not automatically join. I'm trying to look around and confirm that as we speak. That might explain why it wouldn't work and if I manually unjoin the device and rejoin them, it will then enrol
  2. Hi Everyone, I've tried to do some searches here but didn't narrow down to my solution. Story: I've updated my licenses and upgraded Standard to now Business Premium, which now I would be able to enroll and manage my devices. Issue: None of the devices that are currently Azure AD Joined are enrolling into Intune. They still show MDM none and N/A for Compliant. Now, if I would disconnect the user from the device and azure join them again, then the device will become compliant and enroll into intune. Spot checked: verified licenses for the users. verified auto-enrollment for all users enabled MDM. verified on several devices for the Device state to confirm azure AD joined and URL. verified the Device settings that all users can join devices. Checked enrollment restrictions. My Question: It is odd to me that if I Azure AD join a device now, it will work, but none of the current legacy devices before the license upgrade would auto enroll. I prefer not going to each machine and have the users unjoin and rejoin for this to work. Is there anything i'm missing or not catching? Thanks,
  3. Hi, I'm just tapping into Intune and was curious if we can manage Workgroup machines? Thanks,
  4. Right, you could use Cireson Asset Management and create a connector to other Databases and bring over. I have screenshots of how its done and looks like.
  5. @A.Kassem Garth is correct, I wouldn't go about it via CM. SErvice Manager would be able to help with bringing in devices from CM. Then you could use third party like Cireson which has Asset Management tool that plugs into SM. You'll be able to manage your asset lifecycle from there. http://cireson.com/apps/asset-management/
  6. Sorry, yes it was working until they realized Service Manager had gone down after Configuration Manager was installed. After looking through what was going on, they saw that both SM and CM was trying to use port 1433 and for Service Manager, that is not a configurable port. Thanks Garth and quick responses! Doing a site recovery could do the trick for them, and you're right, it is best to have SQL on same site server anyway especially if its stand alone.
  7. Yeah, that's what I thought as well too. Client just so happen to have started the process this way. Luckily this environment is fairly new build, so worse case we could do a rebuild. But to avoid that, if we back up the instance and install SQL on the same Site Server, How do i tell CM to point to the new DB?
  8. Question: Regarding to the Port 1433. We had installed Configuration Manager 2012 R2 to point to the same Database server as Service Manager, but on a different Instance. It come to find out that both SM and CM using Port 1433 is a no go. How would I go about chaing Configuration Manager to point to a new port if i assign it port 1434? Or is it better to just create a new database server for CM and some how to tell it to point to the new Database Server? Thanks,
  9. Hi Guys, Question with Step 5 to create and then Distribute the Configmgr Client package to DP's ... is this still required for 2012 R2 to do? What is the exact reasoning to do this? Thanks,
  10. Hi Guys, I was wondering what is a standard or best practice on setting up the drive partition for a Primary Standalone? The way i'm thinking or have is 4: 1. OS 2. Software Package 3. Software Update 4. Images Does that sound about right? Thanks,
  11. BRS, the step by step guide is very helpful... be sure to read over it few times to understand before actually building it. If possible, build in VM first as practice run.... Other than that you will run into small issues that you can not avoid, but just ask questions and someone will be willing to help. I noticed that you having one drive to have all your packages, apps... etc.. I highly recommend for you to have at about 7 partitions (my opinion). You want to have the Configuration manager installed in separate partition from the local desk drive. then you will have SQL partition for backup, tempDB, log, and Data. all those are its own separate partition. After that I have partition for the DPs and I would store the application under that. This is what I just did, don't know what best practice would be but this made for ease of separation and organization. Thanks
  12. Peter, I'm curious... what would happen if you still have old environment in AD and active? My company upgraded from 2007 to 2012 and currently migrated everything over, but the 2007 environment is still up for a few more months before decommission. What conflict would happen if both environment is stood up and also still in AD? Note: we have already have all clients moved over to the 2012 environment. Thanks,
  13. Guys I have fixed my issue... I went into the regedit and deleted the SMS REG folder. located at: HKLM\software\Microsoft\SMS You would also want to make sure the SQL folder is also deleted in the Programs files of Windows. So, after making sure all is cleaned to near fresh machine again... I ran the secondary creation again from console and I was able to get everything re-installed and read ACTIVE now. Thanks,
  14. Hi Guys, I am having separate issue with deleting secondary. On my first attempt creating Secondary Site Server from the console to a server that is in another region, it passed the prerequisite, but eventually "failed to install". Stupid me, I didn't really pay attention what failed, I just went ahead and did a delete to start over the install from console. When I initiated the Secondary installation for the second time.. it failed to install again, this time I looked at the "show install status" what caused the failure. It showed "Site server or site system role is already installed ......." and "SQL was installed....." So, I went into the server to look and it does show from the first attempt it had successfully installed on the server although the console showed "failed to install". I did an delete again from console and gave it some time to replicate. It was cleared from console, but it does not appear it would delete from the site server itself. This is where i believe i screwed up! I uninstalled manually the SQL server from programs and features first, then the Microsoft System center. Now, when I try to uninstall the Microsoft System Center I get this error: So, I had tried is install Sql express manually hoping Configuration Manager would pick it up and it appears that does not work either. I get the same error message. Anyone have an idea how to remove the configuration manager manually so I could push this through again from the console? Is there any powershell trick to get this done i wonder? Thanks all for help,
  15. Thanks Peter, yeah it is installing. Right now i'm working on finding the issue why is the client finding the old site code from the 2007 environment instead of the 2012 site code. Our old SCCM 2007 has not been decommission yet, but our SCCM 2012 should be the main now. By looking at the Health check log, its doing query AD and installing the old 2007 client. So, i'm trying to find a way to force it to query the 2012.
  16. is Jason's script suppose install the client if we point to where to install from? I'm just wondering if the script detects no client on a machine, if it would automatically install one from a specific path Thanks,
  17. Hi guys, is this Health Check Tool still the one to use and be used in the 2012 CM environment? I found another one by Jason that I understand a bit better but not sure if it works the same? http://blog.configmgrftw.com/configmgr-client-startup-script/
  18. That is freaking Awesome! it worked right away.. Thanks much!
  19. Hi all, I have a little annoying issue. I have created Secondary server but then the server went down. I decided to remove from the console, it appears it has been removed as an secondary in the "Site Hierarchy", but it still shows in the "Sites" as and "Server and site System Role" in the Site Configuration. In the "Sites" it shows that the STATE is still in Deleting. It has been sitting at this state for about 4 days now and won't refresh out of there. Does anyone have an idea how to resolve this, or you think I would be able to just redo the secondary and possibly the console would accept the same name?
  20. Okay, resolution to this was to basically create a new Configuration Manager Package which I did do, but what Microsoft did was basically Re-Create the Client Package as if we built in the CAS. Since my Client package was created in the Stand Alone initially and was Expanded to the CAS it might have caused some issues??? I don't really totally agree with that, but oh well. Here are the Resolution they did: 1. Create a new ConfigMgr client package with any name and no programs (Source: \\server\SMS_Site\Client) 2. Create a new ConfigMgr client upgrade package with any name and no programs (Source: \\server\SMS_Site\Client Upgrade) The packages you created manually will be automatically deleted; no need to remove them later. New default packages will be automatically created. 3. run the following queries in the CAS site database – change the old and new package Ids accordingly: update ClientDeploymentSettings set FullPackageID = 'new Client PkgID' where FullPackageID ='old Client PkgID' update ClientDeploymentSettings set UpgradePackageID = 'new Upgrade PkgID' where UpgradePackageID ='old Upgrade PkgID' 4. Restart SMS_Executive and SMS_Site_Component Services 5. Delete the problematic package after distributing the new default client package to the desired DPs. This is how it looks now: (You will see WFT000D2 is the new Client Package)
  21. HI Guys, This is not an issue question, but more of a Scenario and i guess would be good if it does ever happen to know. Basically, Company 1 has SCCM Environment with CAS and 4 Primaries etc... set up already. Company 2 has StandAlone Primary with secondaries etc.. If Company 1 acquires Company 2, how would you expand Company 2 structure into Company 1? Would this even be possible to do? I thought this would be some of a what easy task, but when I tried in my lab my options for "Install a Config Manager Primary site" or "Install a Config Manager central administration site" are grayed out. Only option i get would be either "Recover a site" or "Uninstall this Configuration Manager site" This is done through both the StandAlone Primary and CAS server. This isn't anything important but just mainly as curiosity of knowledge if this would ever come up since companies do get acquired or sold to another company and I would like to know right off if someone came to me with this type of situation. Plus its fun to think of scenarios just to stay on top of your game. Thanks,
  22. They are still working on the case... I will give update once we or they figure it out.
  23. Hi guys, I have come up with another issue that I have discovered and I have no Idea how this happen or how to resolve it. I actually have a case open with MSFT and it has been two days and they seem to be stuck on this. I notice that the Client Package that was created during the SCCM build is constantly updating. I have image of what i'm talking about below: I know the source version should not be that high and the client should not be updating constantly, seem to be every 4hrs or less its updating. What I have highlighted is the original package that was created during the SCCM build and the one below "SCCM 2012 Configuration Manager Client" is what I created manually which is working and not having a constant update. Thanks,
×
×
  • Create New...