If you’ve recently migrated a VMWare Fusion virtual machine to VMWare ESXi, which itself had multiple disks, you may find that secondary disks don’t show up. You can change this using DISKPART. In my case, this didn’t happen in a Windows 10 VM with two disks, but did happen in Windows Server 2016 with two disks. Weird. Anyway, it’s reasonably easy to fix, using DISKPART. Open a CMD prompt and type DISKPART You should got a ACL type auth warning, just OK It This will open a new console window with DISKPART> prompt Type LIST DISK You should see your various disks listed, and one (or more) will be Offline Type SELECT DISK 1 Type ONLINE DISK At this point, your disk should appear in Windows Explorer If you find you cannot create anything on the disk, then it’s possible it’s readonly, in which case Type ATTRIB DISK CLEAR READONLY That should be everything you need.

Way back in 2012, I dabbled with ESXi. In fact, I faced then, moreorless the same problem I was facing a few days ago. That particular ESXi server didn’t last particularly long - no technical issues, it just didn’t turn out to be the thing I wanted. Fast forward 6 years, and I found myself in a new situation where having an ESXi host would be useful. We use Azure a lot nowadays, but there are still some scenarios where we’d like some on-premise kit such as developing against Sharepoint.

With most things in SQL Server it’s tempting to think you can script it. Because most of the time you can. Recently, I had a requirement to quickly drop everything out of a database (but without actually just dropping the whole database.) The best option I found, was: In the database tree view, find the container for the type of objects you want to delete (e.g., tables) Press F7 to open up the Object Explorer From here, select all the items you want to delete.

In SharePoint 2016, it’s no longer possible to use PSConfig / SharePoint Products Configuration Wizard to provision a single server SharePoint Farm. You’re likely doing this because you just want a single dev environment to… do some stuff. Strangely (more like typically) Microsoft don’t make this particularly easy for you. Assuming you have the basis of a SharePoint server, i.e., : Some sort of OS (i.e. Windows Server) Some sort of SQL Server (i.e., SQL Server 2016) SharePoint binaries installed which isn’t connected to a domain, then you likely fire up the Config Wizard, fill in the obvious entries (ie.

If you’re getting Access Denied for all users even after configured the Super User and Super Reader cache accounts… I recently deployed a new site collection into a new content database. As soon as I tried to hit it, I got unexpected errors. I checked the logs which revealed the familiar stuff about the portalsuperuser and portalsuperreader accounts not being configured - object cache misses and so on, for example: Object Cache: The super user account utilized by the cache is not configured.

I know. Sharepoint 2010. It’s not even. I mean. Just. Look let’s skip past any discussion about why this is happening in 2018, and just cover the issues, OK? So. You’re installing SP2 on a Sharepoint 2010 Farm. This may well apply to any CU in fact. And it possibly applies to SP2013+ also - but at least one of these issues is allegedly caused by a CU that was rolled up in SP2. Right, that’s enough foreplay.

What happens when you let machine learning type automated systems run your consumer communications. Review sites need little in the way of introduction about their popularity or indeed importance to the fabric of the modern Internet. The majority of my online shopping is done on Amazon or eBay and the review / rating mechanisms on each of those (of both the product and the supplier) are invaluable in making a decision. Of course with any user-submitted content, as a consumer you need to know how to read a review - learning how to separate the fake / troll-y tat from the genuine is a bizarre new modern skill.

I’ll cut to the chase. A lot has been written about how to handle large lists and how to handle bulk deleting things. To summarise: getting all items and iterating one by one is *not* the way to do it. The right way to do it is to use the ProcessBatchData method on the SPWeb object. Have done this plenty of times in C# but this time I wanted to cut straight to Powershell. A quick Google later and I found Daniel Root’s boiler plate.

We needed an ’emergency’ night due to an issue with a part of our ‘main’ holiday booking. Found this on Booking.com and the photos and location looked good and near to the port in St Malo so decided to take a punt. Top tip #1 though - book direct with them - not through a third party. It was nearly 60euro more expensive through Booking. Apparently rules have changed recently where the venue had to match the 3rd party price and this no longer applies - so the venue can now charge what they like and it seems the 3rd parties haven’t caught up.

As an aside to my other post on SSRS in SharePoint integrated mode, this is a niggly little issue I encountered. If you find yourself needing to edit a published report and, for whatever reason can’t go back to source to make the change, then a reasonable option is to download a copy of the report from SharePoint and then open it up in your Visual Studio of choice and make the edits. RDL files are pretty great at encapsulating everything they need to run within a single file (they are just XML files, after all) so this is a workable approach.