A note for myself, the product has grown from v7 to v9 now.
Admin Portal Home: https://portal.office.com/adminportal/home
Under that, the different Admin Centers’ URL naming convention is in a quite mess.
Exchange is https://outlook.office365.com/ecp/?rfr=Admin_o365&exsvurl=1&mkt=en-US&Realm=yourcompanyname.onmicrosoft.com
Skype for Business is https://adminca1.online.lync.com/lscp/?language=en-US&tenantID=yourtenaneid
SharePoint is https://yourcompanyname-admin.sharepoint.com/
Under SharePoint, there is an OneDrive document repository for every user: https://yourcompanyname-my.sharepoint.com, it actually resolves to https://yourcompanyname-my.sharepoint.com/personal/yourname_yourcompanyname_onmicrosoft_com/_layouts/15/onedrive.aspx. Other than that, there are sites and teams, and the new stuff – groups.
Default site collection: https://yourcompanyname.sharepoint.com/
Video Portal: https://yourcompanyname.sharepoint.com/portals/hub
Compliance Policy Center: https://yourcompanyname.sharepoint.com/sites/CompliancePolicyCenter
OneDrive is https://admin.onedrive.com/
PowerApps is https://admin.powerapps.com/
Flow is https://admin.flow.microsoft.com/
Security & Compliance is https://protection.office.com/
Azure AD is https://go.microsoft.com/fwlink/?linkid=849449
Two days ago, I got this hit. Probably because I had installed too many apps, or hoarded too much stuff in there. I checked the memory, it was less than 50MB free at one time, then I tried to clean up a little bit, make it about 250MB, but eventually, maybe combined with the low battery situation, my iPad stopped working.
The symptom was like this: it only showed a white Apple logo on the black background, nothing else. I could turn it off by holding the Power button (on right upper side) and Home button (just below the screen) simultaneously, then it went total black. If I push the Power button again, it would show the logo again. There was no third status, even after I tried some other tricks like hold the side volumn button for 5 minutes (upper or down).
I got this iPad mini about four and a half years ago, it is always in good shape, although the memory space is always an issue. Something annoying is that no more OS upgrade on this hardware but the App Store keeps pushing update apps for the newest OS 11. Anyway, I still want to use my iPad mini for a while. So I start looking for solutions.
One of the them I found working was according to this Apple KB – https://support.apple.com/en-ca/HT201263, also this article gave me quite some confidence – https://www.lifewire.com/ipad-recovery-mode-stuck-at-apple-logo-1994540
So this is what I did to revive my iPad mini.
- Have a computer installed with iTunes, update it to the latest version, and login with your Apple id.
- Connect the iPad cable to the USB port on the computer, only the USB end, don’t connect the Lightning end yet.
- Turn off iPad using both Power button and Home button, it should go total black.
- Hold the Home button, you may see the Apple logo come back again, still hold it, and connect the Lightning connector, keep holding, until you see an iTunes logo on the screen with a cable going to it. This means the iPad is not dead yet, you can release the Home button now.
- On your computer, you should see some message update in iTunes, such as it is connecting to an iPad with serial number, memory status, etc. That’s good news.
- The next thing you will see is it prompts you for the next action, because the iPad is not in a very good shape – probably the OS is messed up. There are two options – Update or Restore. I chose Update first, which is some minor repair that won’t wipe out all user data.
- On the top of iTunes, you will see the status and progress – downloading, updating, waiting, etc. My first try failed, it showed me the logo again, so I followed on-screen instructions rebooted both my computer and iPad, repeated steps 2 ~ 7. This time it’s much faster, no downloading , only extracting, etc, and I even saw a grey progress bar under the Apple logo on my iPad. But in the end, it failed again.
- So, I disconnected my iPad, closed and restarted iTunes, and this time I would choose Restore, which is factory restore. I knew I would lose all my data on the iPad, it was ‘dead’ anyway. I still had my backup in iCloud, which shows last backup was done four days ago, not too bad.
- So, I repeated steps above from 2 to 6, and on step 6, I chose Restore and confirmed several times. The iTunes showed the restore progress, then the iPad showed the progress as well in grey bar under the logo. After a little while, it seemed everything was settled down, the iPad went black.
- I gently pushed the home button, the screen went pale and showed “Hello …”
- So, my iPad is back again, like new, and I am happy. Then I waited a bit, with WiFi connection, it should automatically restore as much information as possible from the iCloud.
That was the adventure with my iPad recently, besides that I was not so fortunate trying to revive my Sony reader a few years ago, and reset my BlackBerry Classic early this year went okay, although it started having issues with file manager and language input method lately. Overall, Apple is still the most user-friendly, and I could try the last resort in Apple store, not sure if they would fix out-of-warranty device for free.
Recently I’ve been playing around with the new Hyper-V Nested Virtualization feature within Windows 10 (build 10565 and greater) and Windows Server 2016. It is pretty cool to be able to create virtualized lab environments running that contain Hyper-V clusters. But what if we want a lab that contains VMWare ESXi Hypervisors running on Hyper-V host. I couldn’t find the process documented anywhere and I couldn’t even confirm if it should be possible. But after lots of asking a lot of annoying questions – thanks Adam Burns – Googling and hair pulling I managed to get it going:
So this seems like a good topic for a blog post.
What You’ll Need
You are going to need a few things to get this working:
- A Hyper-Vhost running on Windows 10 (built 10565 or greater) or Windows Server 2016 TP4.
- Enable-NestedVM.ps1 – A PowerShell script for enabling Nested Virtualization in…
View original post 910 more words
A long one, read later, #GNS3, #Linux
A home lab can be one of the most important tools for a network engineer. It can be used to study for certifications, test designs or ideas, and learn new technologies. In years past most network engineer’s home labs would consist of physical routers, switches, and firewalls. With the exponential growth of virtualization, a network engineer’s home lab can be converted into a single physical server that costs far less than having the physical equipment. This blog post will detail the home lab setup that I have created for my own personal use. Most of my blog posts will be using this setup, so if you are interested in recreating what I have done, this blog post will run through all the steps to set up your own home server, or at least show you the tools that I am working with. This is just the basic setup, and any…
View original post 7,555 more words
I was just trying to make a few Windows 10 VM images, so I started to use the same old tool: Sysprep. To my surprise, it didn’t work, while there’s no problem a few days ago on Windows Server 2012 and 2008. This time on Windows 10, it gave this pop up after I ran the same command (in my previous blog).
The log stopped after showing these lines:
SYSPRP Entering SysprepGeneralizeValidate (Appx) – validating whether all apps are also provisioned.
SYSPRP Package Windows.MiracastView_126.96.36.199_neutral_neutral_cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
SYSPRP Failed to remove apps for the current user: 0x80073cf2.
SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing ‘SysprepGeneralizeValidate’ from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2
SYSPRP Shutting down SysPrep log
So I did a little research, found the thread in this forum is quite interesting.
and this as well
Anyway, after tried a few easy steps, I gave up. I don’t really need to clone a bunch of Windows 10 machines, besides install a new Windows 10 client is pretty easy and quick after the evolution of so many generations of Windows.
This issue seems to me a bug in the recent creator update. Microsoft has been trying to unify all its platforms – desktop, surface, phone, even server, but it is still far from there, this time these are a few dev leftover in a public release.