Availability of Update to Windows Intune for Samsung KNOX Standard

I don't understand how Windows Intune supports Samaung KNOX ? KNOX is also a MDM solution, and its security features that enable business and personal content to coexist on the same handset. How to enroll the Samsung KNOX device? Via KNOX
APP or Company Portal from Google Play? BTW, do these two MDM Solution, Windows Intune and Samsung KNOX, exist at same time on the same handset?　Could someone give some ideas?

Intune simply takes over and manages the KNOX layer, it does not add anything to KNOX enabled devices. The COmpany Portal App is just that, a app that enables registration and enrollment of the device and facilitiates the management of the KNOX layer.
This is similar to what happens on other devices including iOS and WP8 where the MDM/management layer is already built into the device.
Jason | http://blog.configmgrftw.com

Similar Messages

Windows Upgrade for Samsung ATIV SE

Wondering when Windows 8.1 will be available for the Samsung ATIV SE?

To Verizon Wireless:
Please help us. If it isn't apparent, your customers are becoming increasingly upset that we haven't been even remotely engaged with any information about the Windows 8.1 update (soon to be 8.1 update 1). Many people, like my wife and I (yes, we each have one), bought this phone on good faith when one of your sales staff told us that the phone(s) would receive the 8.1 update as soon as it was officially released. If I recall correctly, it was something to the effect that the phone shipped with Windows 8 to get the product in the hands of the consumer but that 8.1 was already tested and ready for "immediate" release. This approach would apparently get 8.1 out way faster because it was quicker to push the update over the air than it would be to wait until the official release date and then ship with 8.1 from the factory. Reading the boards, I have a pretty strong feeling that I'm not the only one who got this information for more than one model of handset. To make matters worse, when asked for information you try to placate the masses with an update link (go ahead, click Pamela's response to DeeCT) that doesn't even apply to the specific piece of hardware. If you're going to string us along at least please don't do it with the Samsung Odyssey... why not go all in and link it to the Galaxy S5 or a Blackberry or something? Otherwise, you could simply admit that you told us what we wanted to hear until you got us to to sign. This is the same move that Buffalo Bill pulls in "The Silence of the Lambs" when he tricks the girl into the back of his van. The best part is that everyone else saw it coming: "Probably not a good idea... this sounds shady... his arm isn't broken... why are you getting in the van? Idiot!" Unfortunately, I'm a loyal, long-time customer with few previous issues and took you at your word. I should have done more research into Verizon's reputation for timely updates and general concern for existing customers before I pulled the trigger. Well played. I get to put the lotion on my skin for the next 2 years. Well played.
I apologize for my frustration and bitterness, but I am tired of getting punched square in the groin every time my wife sees the Windows 8.1 "Siri vs. Cortana" commercial, as she reminds me how I convinced her against the iPhone.
That being said, on a positive note, my main gripe isn't with the phone. It's a good piece of hardware and works very well. I just didn't buy it for Windows 8.
Please just tell something... anything. If the phone wasn't successful enough to merit the update just tell us. If it's going to take more time then give us a better estimate than "we have no info". I understand that you have no obligation to provide the update and that the product shipped in working order with the "advertised" operating system, but you should understand that when your sales staff promises an immediate service and you fail to address your customers' concerns... you risk losing those customers.
So, throw me a bone. I just want to know if I get to hear about it during every commercial break for the next two years. Especially when the iPhone 6 comes out. That will be fun... I'm looking forward to that.

Blue tooth driver for windows 7 for samsung galaxy s5

I was told by Samsung that they don't provide the blue tooth driver for Windows 7 for their Galaxy S5 cellphone. They said that the maker of the PC is responsible for that. I don't see any drivers for blue tooth devices of any kind being provided by HP, so I'm thinking that what the Samsung rep can't be correct. Nonetheless, I'm posting this post in hopes someone may know if there 1. is a driver and 2. where to get it. I have a HP Media Center m7050y (PX153AV) CTO Desktop PC that is running Windows 7 Ultimate. I of course have a blue tooth doggle in one of my USB ports and it is working correctly. I know this because I have other blue tooth devices running. Any help will be appreciated.
This question was solved.
View Solution.

Hi,
You have a functioning blue tooth dongle.
Other blue tooth devices are working correctly.
Samsung would have to provide blue tooth driver support. Or contact the blue tooth dongle manufacturer for assistance.
Your HP PC shipped with Win XP. Blue tooth driver support/ hardware was not available when your PC was manufactured.
Jaco
Errare humanum est.

Android update 5.1.1 for samsung galaxy s6

When will the above update roll out OTA

Hi
At the moment we haven't been given a release date for the 5.1.1 update.
As soon as we hear anything we will post something on Community.
It states on the Cash on Tap pages that it's available on the S6.
Do you have an NFC SIM card? They are not sent out as default with the device you do need to request one.
Hope this helps!
Thanks.

Latest update broke window snapping for me...

I cannot hold the Windows key + an Arrow key to get a window to snap any more :( Really annoying for someone who has multiple monitors where dragging to the sides does not work.

Here is a confirmation from MSFT that the snap assist feature is broken in MSFT and will be corrected in future builds (hopefully in 1 month I hope ... guessing ...)
https://social.technet.microsoft.com/Forums/en-US/b82948e0-5a89-49e4-be97-b183fd10ca39/snap-assist-doesnt-work-on-build-9860?forum=WinPreview2014General
We're aware of snap assist and shortcut key problems with 9860. We don't have a workaround at this time, sorry. It is fixed in future builds and we will get that out to you as quickly as we can.
Gabe Aul [MSFT] Microsoft (MSFT)

New window opening for only one standard ESS service

hi everyone,
I am facing a problem with only one standard service Org chart. All other services like who's who , change own data are opening in same portal window. but when i click OrgChart its opening in other window. what could be the problem ? Is it something related backend customization?
Thanks in Advance

Hi ,
Go to tcode SPRO - cross application components - HomePage Framework - Resources - Define Resources -
check window Name property for EMPLOYEE_ORGCHART_SERVICE05, MSS_HCM_SERV_OCI_LAUNCHER,MSS_HCM_SERV_OPROFILE_QUALI_DETAIL,MSS_HCM_SERV_ORGASSIGNMENT,MSS_HCM_SERV_ORG_PROFILES,
window Name property should not contain anything.I am not sure which one is the right resource but do some trial and error.
I suggest not to change the standard resources but create a custom one
Thanks
Bala Duvvuri

Windows Intune support deployment for windows phone (8.1) *.appx files

Hi
We are trying to deploy a windows phone 8.1 appx file with intune (over sccm console). the appx file is signed with a valid symantec certificate.
the installation of the app fails, either when we upload the file as "Required" (so pushing it automatically to the devices) or when we make the app on the company portal app available.
in the sccm console the deployment status says failed -> unkonwn error.
when we use .xap file of an windows 8.0 app, it works like a charm and the xap file is signed with the same certificate.
My question is, is there no support for publishing windows phone 8.1 appx files on Intune? Or what can it be?
Thanks for any hints

UPDATE
According to these links and the comments from Mitch Denny, can somebody confirm that .appx files (company apps) cannot be deployed/installed on windows phone 8.1 yet?
http://blogs.technet.com/b/windowsintune/archive/2014/05/12/what-s-coming-next-with-windows-intune.aspx
http://blogs.technet.com/b/windowsintune/archive/2014/04/28/availability-of-update-to-windows-intune-for-windows-phone-8-1-and-samsung-knox-standard.aspx
I would really appreciate if someone can confirm me this, because im struggling with this since days and there is no official statement from MS.
Thanks

Extensions for Windows Intune are not populating

I have installed the Windows Intune Subscription and Added the Windows Intune Site Connector role. I am trying to manage Windows 8.1 phone, but no extensions have shown up in Config Mgr. Docs say that they will automatically populate. Is
there something that I am missing? Perhaps on the Intune Portal?
Thx.

Jason is right. The update has been carried out to create this Intune extension
http://blogs.technet.com/b/windowsintune/archive/2014/04/28/availability-of-update-to-windows-intune-for-windows-phone-8-1-and-samsung-knox-standard.aspx
Have you seen any extensions previously - this is the third? You will only see them when you open the ConfigMgr console (not if it's already open). If not there is something wrong and you should review the logs Jason has referred to.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Windows Intune Updates?

Dear all,
I have some question with Windows Intune Updates...
Is anyone know where can I find the latest update of Windows Intune?
Like iOS/Android device management, rule compliance...etc.
I need to understand what we can do or what compliance is worked for iOS/Android.
thank you.
Mickey

Intune is not anything you download. It's a service hosted and provided by Microsoft directly. The service is always at the latest stable/production version.
A complete reference of all current policy settings for Windows Intune (stand-alone) is at http://technet.microsoft.com/en-us/library/jj662714.aspx
Jason | http://blog.configmgrftw.com

Windows Intune API

Is there any API available for Windows Intune which allows developers to fetch data or manage mobile devices from outside?

Hi ,
Just to know is there any news or update if windows intune API gonna be released
Thanks
Kalai

Is the August update available in Windows InTune

Is the August update to Windows 8.1 Update 1 available in InTune?

Yes, they are available now.
Thanks,
Jon L. - MSFT - This posting is provided "AS IS" with no warranties and confers no rights.

Email profile support for Samsung Android (KNOX) devices in integrated environment of SCCM 2012 R2 and Microsoft Intune

Hi,
I could see that lot of TechNet articles are being updated recently with the information on Samsung Knox.
Tried to check the email profile configurations in the SCCM console, could not find Android platform in the supported platforms.
I could see this option available when I login to the admin portal of Intune. Can any one confirm if the extension for enabling email profile support for Samsung Kiosk devices id released or planned to be released.
Regards
Leela

Configuring email profiles on Andriod devices is not yet supported via ConfigMgr integrated with Intune, see also:
https://technet.microsoft.com/en-us/library/dn554226.aspx
It probably will be in the future, but there are no dates available yet.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Can't enroll device for user and this user account is not authorized to use Windows Intune.

Hello,
We have SCCM 2012 R2 inegrated with intune via an intune subscription. When I enroll a device with my admin account there are no problems, but when I want to add it with another user account which is a member of the Intune users collection, it can't be enrolled.
When I tested on https://portal.manage.microsoft.com with the credentials of the user I couldn't connect and received the following error: This user account is not authorized to use Windows Intune.
Do I have to do anything in the https://accounts.manage.microsoft.com as there is a checkbox saying Windows Intune. this is unchecked now for all the users even my own account on which I'm able to enroll a device.
Or is this a license problem? I know configuration Manager uses licenses for Intune but where can we track how many licenses are used and how many available? Is there some kind of report available?
I hope someone can help me
Kind regards,
Robben

I added them yesterday and this morning I was still not able to enroll a device with the added user his credentials.
The UPN is correct. Maybe I need to force the DirSync then? Or will one day of waiting be enough normally?
I can see the user in the intune management portal. Does this means it has been synced?
Another thing I noticed is the cloudusersync.log doesn't show them being added? What I was thinking is I first used the all Users collection in the subscription and afterwards I changed it to a specific collection with only the test users. Could it be that
they all synced already and the log doesn't show them anymore?
A warning in this log shows this also:
WARNING: Failed to get lsu url. default release one will be used. exception = System.NullReferenceException: Object reference not set to an instance of an object.~~   at Microsoft.ConfigurationManager.DmpConnector.UserSync.CloudUserUpload..ctor()
SMS_CLOUD_USERSYNC   23/04/2014 15:02:18   7684 (0x1E04)
I don't know if that has anything to do with this?
this is an extract of that log:
CCloudUserSync::Process - User sync processing thread is now stopping.   SMS_CLOUD_USERSYNC   23/04/2014 14:59:42   8144 (0x1FD0)
SMS_EXECUTIVE started SMS_CLOUD_USERSYNC as thread ID 7684 (0x1E04).   SMS_CLOUD_USERSYNC   23/04/2014 15:02:15   7572 (0x1D94)
CCloudUserSync::Process - User sync processing has started.   SMS_CLOUD_USERSYNC   23/04/2014 15:02:15   7684 (0x1E04)
Starting user sync ...   SMS_CLOUD_USERSYNC   23/04/2014 15:02:15   7684 (0x1E04)
WARNING: Failed to get lsu url. default release one will be used. exception = System.NullReferenceException: Object reference not set to an instance of an object.~~   at Microsoft.ConfigurationManager.DmpConnector.UserSync.CloudUserUpload..ctor()
SMS_CLOUD_USERSYNC   23/04/2014 15:02:18   7684 (0x1E04)
Starting user delta sync, raise failure status messages = True   SMS_CLOUD_USERSYNC   23/04/2014 15:02:18   7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:02:19   7684 (0x1E04)
Successfully removed users from cloud 0   SMS_CLOUD_USERSYNC   23/04/2014 15:02:19   7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:02:19   7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:02:19   7684 (0x1E04)
Starting user delta sync, raise failure status messages = True   SMS_CLOUD_USERSYNC   23/04/2014 15:07:19   7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:07:19   7684 (0x1E04)
Successfully removed users from cloud 0   SMS_CLOUD_USERSYNC   23/04/2014 15:07:19   7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:07:19   7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:07:19   7684 (0x1E04)
Starting user delta sync, raise failure status messages = True   SMS_CLOUD_USERSYNC   23/04/2014 15:12:19   7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:12:19   7684 (0x1E04)
Successfully removed users from cloud 0   SMS_CLOUD_USERSYNC   23/04/2014 15:12:19   7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:12:19   7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:12:19   7684 (0x1E04)
Starting user delta sync, raise failure status messages = True   SMS_CLOUD_USERSYNC   23/04/2014 15:17:19   7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:17:19   7684 (0x1E04)
Successfully removed users from cloud 0   SMS_CLOUD_USERSYNC   23/04/2014 15:17:19   7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:17:19   7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:17:19   7684 (0x1E04)
Starting user delta sync, raise failure status messages = True   SMS_CLOUD_USERSYNC   23/04/2014 15:22:19   7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:22:19   7684 (0x1E04)
Successfully removed users from cloud 0   SMS_CLOUD_USERSYNC   23/04/2014 15:22:19   7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:22:20   7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0   SMS_CLOUD_USERSYNC   23/04/2014 15:22:20   7684 (0x1E04)
kind regards,
Robben

Update DISM in WinPE, Windows ADK for Windows 8.1 Update

Windows ADK for Windows 8.1 Update, creates WinPE with DISM version 6.3.9600.16384.
Latest build of Windows 8.1 Pro Build 9600, dated 22/11/2014, has DISM version 6.3.9600.17031.
Have run the Windows ADK setup again, but says NO Updates available.
Have created listings of all the DISM files in WinPE and Windows 8.1, but reluctant to copy files across, as I assume that registration / registry changes are also required.
Does anyone know how we can update the version of DISM in WinPE to 6.3.9600.17031?
Thanks, John

DISM files in Windows 8.1...
WIN-P1V1BFHNLTV C:\Windows\dism*
Sun 19/04/2015 19:02:12.11 Administrator RNDIR 1.5.2.49 10-Apr-2015 C:\Windows\dism*
C:\Windows\Logs\DISM
C:\Windows\Logs\DISM\dism.log
C:\Windows\Prefetch\DISM.EXE-D9E524DA.pf
C:\Windows\Prefetch\DISMHOST.EXE-598C5A9E.pf
C:\Windows\System32\Dism
C:\Windows\System32\Dism.exe
C:\Windows\System32\DismApi.dll
C:\Windows\System32\Dism\DismCore.dll
C:\Windows\System32\Dism\DismCorePS.dll
C:\Windows\System32\Dism\DismHost.exe
C:\Windows\System32\Dism\DismProv.dll
C:\Windows\System32\Dism\en-US\DismCore.dll.mui
C:\Windows\System32\Dism\en-US\DismProv.dll.mui
C:\Windows\System32\en-US\Dism.exe.mui
C:\Windows\System32\en-US\DismApi.dll.mui
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism\Dism.Format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism\Dism.psd1
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism\Dism.psm1
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism\Dism.Types.ps1xml
C:\Windows\SysWOW64\Dism
C:\Windows\SysWOW64\Dism.exe
C:\Windows\SysWOW64\DismApi.dll
C:\Windows\SysWOW64\Dism\DismCore.dll
C:\Windows\SysWOW64\Dism\DismCorePS.dll
C:\Windows\SysWOW64\Dism\DismHost.exe
C:\Windows\SysWOW64\Dism\DismProv.dll
C:\Windows\SysWOW64\Dism\en-US\DismCore.dll.mui
C:\Windows\SysWOW64\Dism\en-US\DismProv.dll.mui
C:\Windows\SysWOW64\en-US\Dism.exe.mui
C:\Windows\SysWOW64\en-US\DismApi.dll.mui
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism\Dism.Format.ps1xml
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism\Dism.psd1
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism\Dism.psm1
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism\Dism.Types.ps1xml
C:\Windows\WinSxS\amd64_microsoft-windows-d..anagement.resources_31bf3856ad364e35_6.3.9600.17031_en-us_cac7f03ebc6b27c5\Dism.exe.mui
C:\Windows\WinSxS\amd64_microsoft-windows-d..cing-management-api_31bf3856ad364e35_6.3.9600.17031_none_97b32ab0331d7369\DismApi.dll
C:\Windows\WinSxS\amd64_microsoft-windows-d..ement-api.resources_31bf3856ad364e35_6.3.9600.17031_en-us_0393f46435b92988\DismApi.dll.mui
C:\Windows\WinSxS\amd64_microsoft-windows-d..ervicing-management_31bf3856ad364e35_6.3.9600.17031_none_4f9af566e17dbc2c\Dism.exe
C:\Windows\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_1c257853fe906c1a\DismCore.dll
C:\Windows\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_1c257853fe906c1a\DismCorePS.dll
C:\Windows\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_1c257853fe906c1a\DismHost.exe
C:\Windows\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_1c257853fe906c1a\DismProv.dll
C:\Windows\WinSxS\amd64_microsoft-windows-d..ment-core.resources_31bf3856ad364e35_6.3.9600.16384_en-us_02b013759532eb99\DismCore.dll.mui
C:\Windows\WinSxS\amd64_microsoft-windows-d..ment-core.resources_31bf3856ad364e35_6.3.9600.16384_en-us_02b013759532eb99\DismProv.dll.mui
C:\Windows\WinSxS\amd64_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_9ce1bd3c3df000d6\Dism.Format.ps1xml
C:\Windows\WinSxS\amd64_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_9ce1bd3c3df000d6\Dism.psd1
C:\Windows\WinSxS\amd64_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_9ce1bd3c3df000d6\Dism.psm1
C:\Windows\WinSxS\amd64_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_9ce1bd3c3df000d6\Dism.Types.ps1xml
C:\Windows\WinSxS\x86_microsoft-windows-d..anagement.resources_31bf3856ad364e35_6.3.9600.17031_en-us_6ea954bb040db68f\Dism.exe.mui
C:\Windows\WinSxS\x86_microsoft-windows-d..cing-management-api_31bf3856ad364e35_6.3.9600.17031_none_3b948f2c7ac00233\DismApi.dll
C:\Windows\WinSxS\x86_microsoft-windows-d..ement-api.resources_31bf3856ad364e35_6.3.9600.17031_en-us_a77558e07d5bb852\DismApi.dll.mui
C:\Windows\WinSxS\x86_microsoft-windows-d..ervicing-management_31bf3856ad364e35_6.3.9600.17031_none_f37c59e329204af6\Dism.exe
C:\Windows\WinSxS\x86_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_c006dcd04632fae4\DismCore.dll
C:\Windows\WinSxS\x86_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_c006dcd04632fae4\DismCorePS.dll
C:\Windows\WinSxS\x86_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_c006dcd04632fae4\DismHost.exe
C:\Windows\WinSxS\x86_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_c006dcd04632fae4\DismProv.dll
C:\Windows\WinSxS\x86_microsoft-windows-d..ment-core.resources_31bf3856ad364e35_6.3.9600.16384_en-us_a69177f1dcd57a63\DismCore.dll.mui
C:\Windows\WinSxS\x86_microsoft-windows-d..ment-core.resources_31bf3856ad364e35_6.3.9600.16384_en-us_a69177f1dcd57a63\DismProv.dll.mui
C:\Windows\WinSxS\x86_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_40c321b885928fa0\Dism.Format.ps1xml
C:\Windows\WinSxS\x86_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_40c321b885928fa0\Dism.psd1
C:\Windows\WinSxS\x86_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_40c321b885928fa0\Dism.psm1
C:\Windows\WinSxS\x86_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_40c321b885928fa0\Dism.Types.ps1xml

How to create recovery disk for windows 8.1 after update from windows 8.

My laptop came with windows 8 and i have recovery discs for windows 8.
Now i've updated to windows 8.1, so i want to creat recovery discs for windows 8.1.
So in future when i use recovery discs i dont have to download windows 8.1 again.
Please tell me if there is any way to do this.....

As colakid posted, in Windows 8 the ability to create a recovery CD/DVD has gone. Your options are to:
create a recovery USB; or
create a recovery image.
Recovery USB
Colakid's post talks you through how to make a recovery USB: from control panel, choose Recovery, then Create a Recovery Drive, and follow the prompts.
However, the 'recovery USB' can be a bit misleading. When the wizard starts, there is an option to 'copy the recovery partition from the PC to the recovery drive'. If you do not check this option, you will still need installation media to reset your PC.
Since you have upgraded from Windows 8 to Windows 8.1, you will probably not be able to check this option, as it will be greyed out (like it is in the picture in Colakid's post).
If you go ahead and create the USB anyway, you will be able to boot to it, but you won't be able to reinstall Windows unless you have the installation media (or possibly a system image, though I haven't tried that).
Recovery image
The recovery image is an image of your computer that Windows will use when you select the 'refresh my pc' option. You can create a recovery image using the recimg.exe tool.
First, open an elevated command prompt (type cmd and press Ctrl + Shift + Enter).
Next, create the recovery image by typing:
recimg /createimage [path]
Where [path] is the folder you want the image in, eg C:\Recovery. You cannot set the file name - it will always be called CustomRefresh.wim.
Let it run its course. When it's done, you can check that it is the current recovery image by typing
recimg /showcurrent
It's important to keep in mind what a recovery image contains. It will have your Windows system files (in their current state), and the desktop apps you have installed (so it makes sense to do this after a fresh install of Windows). It will
not backup any Metro apps or user files, because these are not deleted during a system refresh. If you want a complete backup of everything on your computer the way it is now, you should make take a complete system image (which
can be done from the File History settings in control panel - at the bottom left there will be a 'System Backup Image' option - or you can do it using any other backup software like Ghost or Acronis).
In my case, I created the recover image straight after upgrading to Windows and it was about 6 GB.
Prepare/Create and register an recovery partition, so the option Copy the Recovery Partition becomes available in the recovery drive UI application.
In elevated command run> RECIMG -CREATEIMAGE C:\REFRESHIMAGE<
This will create a new custom.wim in a folder Refreshimage.
Now lets get ready to register the path of the image, so our create recovery drive option(COPY THE RECOVERY PARTITION FROM THE PC TO THE RECOVERY DRIVE) becomes available.
> In the folder you created there will be a> custom.wim<
change it to>INSTALL.wim<
> Create a folder In Cd/directory using Elevated command> mkdir c:\Win8.1-Recovery,>
Win81-Recovery<.
> Copy the INSTALL.WIM. Put in the Win81-recovery folder created.
> Run in elevated commad>REAGENTC /SetOSImage /Path C:\Win81-Recovery\INSTALL.WIM /Index 1<
Do not copy the arrows if using copy and paste, that is my way of pointing out lines of code
Information provided by the link below, thanks Keith. I simplified the process for easy following and added my own tweak from trial and error for the install.
blogs.technet.com/b/keithmayer/a···ive.aspx

Availability of Update to Windows Intune for Samsung KNOX Standard

Similar Messages

Maybe you are looking for