| I had a customer who wanted me to install SharePoint 2013 on a Windows Server 2012 which was not connected to the Internet. So it was not just a case of winding up the Prerequisite installer and off we go. Oh No.
The Prerequisite installer consists of at least two parts :-
- Configure the Roles and Features of Windows Server 2012
- Install all of the required updates so that SharePoint 2013 will work
The first of these two turned out to be the biggest problem.
To go back to the start, I am a great believer in Brian Lalancette's autospinstaller. I have been using it ever since it came out.
There is a SP2013 version publicly available to all. For the purposes of this install I was using a Beta (Version 98528) which Brian assures me is good enough to use on production environments.
(It also fixes a number of issues with the installation of SP2103 Search). Version 98528 (and presumably beyond) requires an updated version of the AutoSPInstaller Input file.
In this version (98528) you need to set the version of SharePoint you are installing to SP2013 <Install SPVersion="2013">.
For an "Offline" install (ie no Internet available) you need to set OffLine to True <OfflineInstall>true</OfflineInstall>
You should check the service apps at the bottom of the file as these have changed.
The Next thing you have to do is to configure the Windows 2012 Features and Roles. As I said before this was the tricky bit.
You need to have the Windows Server 2012 installation media mounted. I used Craig Lussier's script for configuring the Roles and Features of Windows Server 2012.
http://gallery.technet.microsoft.com/office/DownloadInstall-SharePoint-e6df9eb8 .
I used his first PowerShell script and it takes a parameter which is where is the sources\sxs resides on the Windows Server 2012 installation media.
Next you need to get the Prerequisites. I used another machine on which I executed Craig's second PowerShell script.
I copied these files to \SP\2013\SharePoint\PrerequisiteInstallerFiles\ where \SP\2013\SharePoint is the SharePoint 2013 installation media.
Finally there is a "gotcha" you also need a further "HotFix" Windows8-RT-KB2765317-x64.msu. Again, download this on another machine and copy it to \SP\AutoSPInstaller\Hotfixes\
So you PreRequisites folder should look like this :-
So once we have all of this preparatory work done. We can finally run AutoSPInstaller.
It runs, has a single reboot once the Prerequisite Installer has completed and it then runs to completion. Assuming that everything in the AutoSPInstallerInput.xml file has been has been configured correctly. |
| I have been using the preview version of Office 365 now since last July. When it first appeared I thought I was doing something wrong. I could not create any subsites on the Public version of the website. I looked at the various blogs and could not find what I was doing wrong. Finally on an office 365 forum I found what I was looking for (but not happy what I found). The public web site was intentionally modified not to allow people to add new subsites ! How many people will want to use a public web site which only allows you to have 4 pages and a blog ! I can see why Microsoft have done this, if they give people too much slack then there will be very large web site with thousands of hits a day which could well cause performance problems with the site. However, I think there could be a compromise - let there be one or two levels of subsites, whilst restricting those who try and abuse the system with large web sites. |
|
When I first started in this industry 40 odd years ago, I used to log onto my terminal which was an old ASR 33 (we used to call them clatter clatter bang bangs – because they were very noisy). I could run available programs. If the program I wanted was not available I could write my own, it was Algol 60 and Fortran 4 then. I would write them, compile them, compose them (ie make them into a runnable program) and then run them. The computer then was an ICL (Now Fujitsu) 4-70, running an operating system called Multijob in a large air-conditioned computer room. I got know Multijob quite well a few years down the road as I ending up supporting it when I worked for ICL. The university I went to (and subsequently worked for) was UWIST (University of Wales Institute and technology) which was part of SWUCN (The South West University Computer Network – the pre-cursor to JANET – the academic network) and we used to “rent” time on the ICL 4-70. Fast forward a few years and I was working for a large American corporation called Computer Sciences Corporation (CSC). They had a time sharing network called INFONET. Customers would rent time on this time sharing network to run their programs on and were charged accordingly.
Then the personal computer came along and a young upstart called Bill Gates invented an operating system called MS-DOS and a company called IBM invented the IBM-PC 64K RAM with either 5 inch or 3.5 inch floppy disks which effectively killed off the time sharing networks like MULTIJOB, CICS, and a host of others as users could now write their own programs using Fortran 77, C etc. They did not need a big expensive mainframe with a not very fast communications line. They could do everything themselves. Then COMPAQ (as it was then – now HP) started bringing out servers. Microsoft started to bring out Windows NT and the concept of servers was born. Servers were housed either in companies or even departments so that users could access these servers using Ethernet cabling running at 10Mbps or even 100bps. I remember racks of these servers in computer rooms – still air-conditioned. But they were comparatively cheap to buy and cheap to run.
Then a few years Microsoft started bringing out BPOS and Azure and Amazon bought out the EC1 virtual servers. People started to use these “cloud” services, where large server farms, sometime housed in what look like freight containers were becoming ever popular and we now come round to the modern day where Microsoft have just announced that Office 2013, including SharePoint 2013, has gone “RTM”. I am not sure what “RTM” means now as long gone are the days of manufacturing Cds or DVDs containing software. Software is now downloaded off the Internet and all you do when you go and buy your “software” is buy some packaging with a licence key on it, which you enter when you have downloaded your software. It is rumoured at the SharePoint 2013 could be the last major on-premise version of SharePoint as SharePoint online can now do almost everything that SharePoint 2013 on premise can do. Microsoft have now released pricing for Office 2013 and for the first time since the early 2000’s the price of Office has increased. It is now significantly cheaper to “buy” Office 2013 “in the cloud” than it is to buy Office 2013 from your local PC shop. Microsoft’s pricing is now making the “the cloud” financially more attractive than buying Office itself.
But hang on a minute, we are now back where we started, users logon to their terminals and they use programs which are housed in huge server farms miles away and if there is not a program which does what they want then they can build it using C# or Java, compile it and run it. So we are back where we were 40+ years ago ! What goes round comes round.
|
| SQL 2008 installs in a state that will stop you connecting to a named instance
This is not done out of badness, but for security.
This is an old one but still catches people out !
To fix this :-
Start SQL Server Configuration Manager
Expand the SQL Server Network Configuration node and find the Protocols for your Instance
If they are not enabled Right click on TCP/IP and click Enabled - do the same with Named Pipes
Right click on TCP/IP and click Properties. Select the IP Address tab and make a note of the TCP Dynamic Port
Restart the SQL server service
When you connect to a SQL Server instance via TCP/IP the connection attempt will query the SQL Server Browser service (on port 1434) and find out which port a specific instance is set to listen on. However by default the SQL Server Browser service is disabled. You can now either start it or use the Port number you found earlier to connect directly.
Confusingly the syntax is different to what you may expect – no semi-colons here, use a comma so on the screen where the configuration wizard asks you for the database server enter :-
ServerName\InstanceName,PORT
|
| Just a quick one….
In preparing my previous post I hit a major problem – I could not get Word 2010 to talk to my blog on SharePoint 365.
Every time I try and create an account using Word 2010, it fails. I tried most things, I bing'd it I could not find a solution.
In the end the only solution I found which worked was to wind up SharePoint Workspace 2010 and create an account with the exact name as the one which I have on my blog.
Once I had created the account and sync'd the site, I tried to create the account again using Word 2010. This time it worked ! |
| Windows Server 8 Beta has been out for a couple of months now so I decided to see if I could run SharePoint 2010 on it. To make things more interesting I decided to use SQL 2012 as the database engine.
So I downloaded Windows 8 beta from http://technet.microsoft.com/en-us/evalcenter/hh670538 .
I was using VMWare Player so I created a new VM converted the Hyper-V image to a VMware image by using StarWind V to V convertor http://www.starwindsoftware.com/converter and attached the disk to the VM.
I started the VM and Windows 8 Server started to load, it rebooted and I was ready to Rock and Roll.
When Server 8 had loaded and I had logged in I got the "Server Manager" screen.
I navigated on the left hand menu to "Local Server" :-
Click on Domain and add the VM to your favourite (development) domain.
Next get the SQL 2012 trial from http://www.microsoft.com/en-us/download/details.aspx?id=29066 . But before you install that on your band new Windows 8 Server, you need to enable the .NET framework 3.5 feature.
However, if you do it from the command line :- dism /online /enable-feature /featurename:NetFx3 /source:d:\sources\sxs\ after restarting the system, when I went into the Server Roles and Features wizard, the .NET 3.5 feature was still not enabled. So I stepped through the wizard to add the feature, and rebooted again. This time it worked !
I then went through the SQL Server setup and, once I had made all of my feature and other configuration selections, it took about 12 minutes to install SQL Server 2012. When it was finished, it had placed a whole slew of tiles onto the Metro start page (hit the "Windows" key to get this) :
So we now have our SQL Server. So now time to get the SharePoint 2010 server running.
So I repeated the above for the creation of the second Windows Server8 VM. I got the SharePoint 2010 trial from http://www.microsoft.com/en-us/download/confirmation.aspx?id=13768 I doubled clicked on it and got this screen :-
Oops ! so I Bing'd it and all I could find was this French blog - http://blog.hand-net.com/sharepoint/2010-06-10-error-lors-de-linstallation-des-office-web-apps-2010-sur-windows-7.htm
Note this blog talks about installing SharePoint 2010 web apps on Windows 7.
This is the difficult bit !
In Windows Server 8 Beta, ServerManagerCMD.exe is depricated, isn't supported and isn't shipped. However, the SharePoint 2010 installer requires it - you can read up more on this at tool at http://technet.microsoft.com/en-us/library/cc732757.aspx  . PowerShell cmdlets will take its place moving forward.
So I have to give the credit regarding where I found this part of the solution to the above web site .
The post is in French, but essentially what the author says is that the installer calls ServerManagerCmd.exe and waits for a particular return code: 1003. If you simulate this, you can trick the installer into sufficiently thinking that ServerManagerCMD.exe is actually there doing what it was designed to do and this will allow the SharePoint 2010 install to proceed.
The necessary c# code is here :-
namespace NJPEnterprises.ServerManagerCmdEmul
{
class Program
{
static void Main(string[] args)
{
System.Environment.ExitCode = 1003;
}
}
}
As a side note, this is also a reason why the Prerequisite installer fails - it also uses ServerManagerCMD.exe to configure the IIS Roles and Features. Since ServerManagerCMD.exe doesn't exist there are issues. Beyond that, the SharePoint 2010 installer won't install all of the correct Roles/Features required within Windows Server 8 Beta even if you did get it to work. So we need a powershell script to do all of this. Fortunately there is such a powershell script which can be downloaded from Technet - http://gallery.technet.microsoft.com/SharePoint-2010-and-dee17600 . This powershell script does the following :-
So try again with the SharePoint install. This time it worked. So a quick reboot and we are ready to run the configuration wizard.
This is where the next set of problems occurred.
I got as far as entering the database server name, but I could not connect to the database server. It was there, I could ping it but the SharePoint Configuration wizard could not find it.
So check the SQL Server and specifically check the Firewall. Surprise, surprise port 1433 was not open for incoming packets. So try again and we get a bit further but then get the error that stored procedure sp_dboption not found. I have seen this one before – we need SP1 so I download SP1, run it, and reboot we are off again. This time the configuration wizard works.
So here we are :-
Proof that SharePoint 2010 plays nicely with Windows Server 8 and SQL 2012.
BTW – as we have to do some klugs I suspect that Microsoft might not support this configuration.
I am not going to claim this was all my own work and I leaned heavily on the following blogs :-
http://blog.hand-net.com/sharepoint/2010-06-10-error-lors-de-linstallation-des-office-web-apps-2010-sur-windows-7.htm
http://blog.furuknap.net/sharepoint-2010-running-on-windows-server-8-beta
http://gallery.technet.microsoft.com/SharePoint-2010-and-dee17600
|
| In this scenario I be referring to a consultancy who's known as The Acme SharePoint Consultancy and they have a number of SharePoint-guys and possibly a rock star or two (or more !) so when it comes to:
1. Troubleshooting those SharePoint logs to get the Search working again for a customer
2. Resolving site provisioning errors when the customer has been stuck on it for days
3. The company who can put a bunch of JavaScript into a Content Editor Web Part and eliminate the need for a 3rd party component
…. Etc etc
Their consultants mostly come from a .NET developer background and have picked up a lot of infrastructure knowledge while working with SharePoint over time (usually they have been working with SharePoint since SharePoint Portal Server 2003 or even earlier)..
Looking back a few years, that could easily be your company. SharePoint seemed to be mainly sold to the IT department within organizations and the key product features were:
- Great set of collaboration features
- Performance
- Scalability
- Integration with the rest of the org applications
All the consultants needed to know (not that it was easy to learn) was what SharePoint does out-of-the-box and how to configure or customize it when needed. The set of features was pretty simplistic and once you get a hang of it – you`re good, you got a few projects under your belt and you got yourselves a reputation and business was good.
But then as SharePoint penetrated deeper within a typical organization, various business users and business decision makers started requesting more than just a simple set of collaboration features. So, new features seemed to be gradually accommodated and more and more users were on board. So projects had more users, used a more complex set of product features, which resulted in even more requests.
Then came SharePoint 2007, SharePoint was no longer a collaboration application, it`s even way more than below, but here are just a few functional areas:
- Business Intelligence
- Publishing and collaboration
- Mobility
- Accessibility (in terms of business data etc)
- Search
- Excel services
… and many more
Then with SharePoint 2010 there was even more integration including Project Server and via the Business Connectivity services, I can only imagine there will be more products to join the stack.
With more functionality being added to the product at each release, more skill diversity will be required to make full use of the product
All of the sudden the sales people and the pre-sales consultants need to talk about things like:
1. Change Management
2. Governance
3. Compelling and slick design
4. Performance, of course, doesn`t go away
5. Disaster Recovery
… etc, you get the point, the sales presentations and the ensuing conversations are no longer just a tech talk.
So what`s the conclusion and how to keep up with all this, do we just keep learning ?
So what will the SharePoint Consultancy of the future be (well this is my view)
- Consultancies will specialise in different functional areas (Infrastructure, BI, Development, User Interface Development, Publishing web sites, Extranets etc).
- Areas like Requirements gathering will be outsourced to specialist companies eg 21Apps and their Innovative Games methodology
- Maybe testing will be outsourced as well to specialist companies.
- Some consultancies will specialise in Vertical Markets eg Public Utilities, Financials, etc
- Some consultancies will even specialise in functional areas within vertical markets
Of course there will be some who will pick several discipline or product areas, but remember with the product constantly evolving – they may end up being an expert in nothing and that's a huge step away from the original-SharePoint-Consultancy. The point I am making is that SharePoint has now got too big to be handled by one company (unless you are one of the major consultancies with experts in all SharePoint areas) and so to survive, consultancies will have to pick and choose which areas they operate in and which vertical markets they will specialise in.
Comments are welcome, I would love to hear from you either via the comments form or via Twitter @Nigel_Price
NB The Acme SharePoint Consultancy is purely a fictional consultancy and bears no resemblance to any company currently (or has ceased) trading.
|
| I have been involved in SharePoint for about 10 years now and over the years I have come to have issues with certain aspects of SharePoint Solutions and these tend to be in the area of Supportability and maintainability.
SharePoint Designer changes should be done in a controlled manner.
The flexibility of SharePoint can actually become an issue once the solution has been deployed and is up and running in a production environment. Changes made with SharePoint Designer can be made without much effort. However, how do you do proper QA of that change and then move the change from say a test to a production environment. It is not straight forward. It's very important to keep this issue in mind when defining the policies for how, when and who makes changes to what using what tools.
The way Microsoft is marketing and selling the SharePoint platform can be a problem in itself. You need to make changes to the look and feel of your intranet? Easy, with SharePoint Designer you can do it! And you do not need to be dependent on expensive consultants and highly paid developers who are the only ones that know how to do even the simplest change in the systems? and they realize that and hold you to hostage ?
You DO NOT want people to make changes to the production system by hand (ie by using SharePoint Designer). The scope for making a mistake is enormous. There is no way you can do a proper QA on that change and there is no change management, no regression path no nothing. This is an unacceptable situation and I hope one of the things that come out in SharePoint 15 is a better way of moving SharePoint Designer changes from one environment to the next, ideally via a wsp.
I accept that what a site administrator does with their own site is up to them and if they want to screw their site up with SharePoint Designer then that's their problem. However, where the change is to a business critical part of the site, then proper change control procedures must be used and SharePoint Designer should not be used. There needs to be very clear guidelines on what can be done by a site administrator and what has to be done under a proper change control procedure. The right way to go depends on many factors, such as how business critical the application is, the amount of custom code that depends on i.e. certain columns and lists being in place, where the responsibility lies if something goes wrong and end user knowledge of the platform and tools.
There must be a governance plan in place that should address these issues.
Take into account supportability when you design a solution.
I recently was involved in a project where there were over 150 sites in it and each site had the same list and that list had a list workflow on it. I was asked to make an amendment to add a column to the list and then to amend the workflow to include that column. Adding the extra column was fairly simple for new instances of the list. The problem comes when you have to add the column to existing lists. You have to write some powershell script to go around all of the sites, find the list, and add the column to the list. Then, you have to update the workflow on the list. But hang on, it's a SharePoint Designer workflow, do you have use SharePoint Designer to update 150 lists ?
A better solution would be to have a single, common event receiver which kicked off a single workflow. This way you only had to update the workflow once. So the moral of this story is to remember the poor person who has to maintain your solution when you design it.
Make it easy to upgrade to the next version of SharePoint
The upgradeability factor is always important to keep in mind, but it's becoming more and more important as the next version of SharePoint (SharePoint 15) is almost upon us.
As a rule, the SharePoint Team puts a lot of efforts to ensure the backwards compatibility of the platform. This means that upgrading an out of the box solution or a site with few customizations to the next version of SharePoint is often a very straightforward process (at least from my experience from upgrading solutions from 2007 to 2010). However, UI customizations and custom developed components will add additional effort though. This is particularly true for CSS "hacks" on top of the out of the box styling. The issue here is that certainly when upgrading 2007 to 2010 Microsoft changed the rendering so that what worked with 2007 did not necessarily work for 2010 as 2010 is Web 2.0 "AA" compliant. So therefore minimize as much as possible these hacks because they will come back and bite you when you upgrade. |
| A recent blog posting by Ian Woodgate of PointBeyond set me thinking about how SharePoint projects should be run. I come from the old school of developing solutions and the waterfall way of running projects. In this methodology the project plan consisted of a number of releases, each one building upon the last one. The first release was always the initial release and its objective was to get something out to the users early so they could get used to the new system. Each subsequent release then built on that first release adding new functionality everytime there was a new release.
Unfortunately, SharePoint Projects I have been involved in over the years ( SharePoint Portal Server 2003, MOSS 2007 and SP2010), have involved a long first phase before the first release. This resulted in a "Big Bang" of functionality for the first release. (I was always taught small incremental releases.) It then followed on that there would be a large amount of feedback from the users, some of which demanded changes to the initial release. So now, not only did we have phase 2 to design, write and test, but inevitably the customer wanted their changes incorporated into the next release as well. Yes, I know at this point the Change Request procedure kicks in and all of that entails. The end result of which usually means that the second phase gets delayed and the project itself gets delayed and the total cost of the project has increased from its initial value.
Surely, a better way of running these projects would be to roll out as much of the functionality that is Out of the Box as possible for the first phase Leave the custom code until a later phase. This way the users can get used to SharePoint at an early stage of the project.
In my presentation to #SPSUK "Why do we develop – because we can ?" I suggested that one of the reasons why people dive into Visual Studio right from the "off" is that they do not know what is available "Out Of The Box" so they start coding straight away when all they had to do was look inside SharePoint to find the functionality they want. The other reason, I have found, that people dive for Visual Studio at the first sign of a requirements specification, is that they are unable to give the customer exactly what they want UI wise. If, instead they went back to the customer and said look if you want this exact user interface it will cost £x but if we changed the UI slightly to this then the cost will be considerably less (in terms of development, testing and risk). Most customers would say "yes" we will go with the OOTB UI, because it saves us money and the risk of the project being late is reduced.
I worked on a project for a customer recently where they took just that attitude. They wanted an extranet up and running within a month. So I said that's fine but two things :- 1) The site is going to have to be out of the box with no custom code and 2) There might need to be some compromises on the UI to ensure that item 1) is adhered to. The result was that after the "Look and feel" people did their stuff, we created a CKS:DEV branding project to take the css file, the images, the master page and the page layouts. Modified the Master Page and the Page Layouts to give the user the look and feel they wanted and within a month we had a working extranet. In subsequent releases we added more page layouts and more functionality so that at the end of the project they had a fully functioning extranet which was launched on time and within budget. Not a single line of C# code was written for the project.
So, in summary, when you are talking to the customer about their requirements try and explain the cost (and the risk) of using custom code and explain that with some small changes to the UI they can save a lot of money. Make sure that the first release contains OOTB functionality only and then build the custom stuff in a later release.
|
| I had a problem recently where customers were complaining that they could not create folders within a MOSS 2007 document library and get them approved when the folder was created from Microsoft Word 2003 or Word 2007. However, when I created the folder using the MOSS 2007 document library GUI it created the folder and approved it using the "additem" event handler I had created.
Upon investigation the difference between the two scenarios was that with the MOSS 2007 Document Library GUI method the properties parameter passed into the event hander by MOSS 2007 had the SPItemEventProperties.ListItem object populated. Whereas when the folder was created using Word 2003 or Word 2007 then it was NULL ! (I am told this occurs when MOSS 2007 does not have a context to work with.)
So to fix the problem I changed the event handler to look like this :-
private void ItemHandleEvent(SPItemEventProperties properties)
{
try
{
if((properties.ListItem == null) || (properties.ListItem.ContentType.Name.ToLower() == "folder"))
{
// Its a folder
if (Trace.TraceLevel.TraceInfo)
{
Trace.Write(this, "ItemHandleEvent ContentTypeName = Folder ");
}
DisableEventFiring();
SPSecurity.RunWithElevatedPrivileges(delegate()
{
using (SPSite site = new SPSite(properties.WebUrl.ToString()))
{
using (SPWeb web = site.OpenWeb())
{
SPList doclib = web.Lists[properties.ListTitle];
SPFolder thisfolder = web.GetFolder(properties.AfterUrl.ToString());
SPModerationInformation moderationInformation = thisfolder.Item.ModerationInformation;
if (Trace.TraceLevel.TraceInfo)
{
Trace.Write(this, "ItemHandleEvent modeationinformation = " + moderationInformation.Status.ToString());
}
if (!(moderationInformation.Status == SPModerationStatusType.Approved ))
{
moderationInformation.Comment = string.Format("This folder has been approved on the {0}", DateTime.Now);
moderationInformation.Status = SPModerationStatusType.Approved;
thisfolder.Item.Update();
Trace.Write(this, "ItemHandleEvent " + string.Format("This folder has been approved on the {0}", DateTime.Now));
}
}
}
});
}
}
catch (Exception ex)
{
Trace.Write(this, "We got an exception in Document Event Handler" + ex.Message);
}
finally
{
EnableEventFiring();
if (Trace.TraceLevel.TraceInfo)
{
Trace.Write(this, "ItemHandleEvent Finally");
}
}
} |
Compliance Details javascript:commonShowModalDialog('{SiteUrl}'+
'/_layouts/15/itemexpiration.aspx'
+'?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+
'/_layouts/15/hold.aspx'
+'?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+
'/_layouts/15/Reporting.aspx'
+'?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+
'/_layouts/15/expirationconfig.aspx'
+'?ID={ItemId}&List={ListId}'); return false;}}, null); 0x0 0x1 ContentType 0x01 898 Document Set Version History /_layouts/15/images/versions.gif?rev=26 javascript:SP.UI.ModalDialog.ShowPopupDialog('{SiteUrl}'+
'/_layouts/15/DocSetVersions.aspx'
+ '?List={ListId}&ID={ItemId}') 0x0 0x0 ContentType 0x0120D520 330 Send To other location /_layouts/15/images/sendOtherLoc.gif?rev=26 javascript:GoToPage('{SiteUrl}' +
'/_layouts/15/docsetsend.aspx'
+ '?List={ListId}&ID={ItemId}') 0x0 0x0 ContentType 0x0120D520 350
|
About this blog
 |
| Welcome to my new Blog as the old one seems to have disappeared. I will try and retrieve as many of the old posts as I can. The dates might not be quite right. Anyway I will be blogging about my experiences with SharePoint and everything SharePoint. |
Compliance Details javascript:commonShowModalDialog('{SiteUrl}'+
'/_layouts/15/itemexpiration.aspx'
+'?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+
'/_layouts/15/hold.aspx'
+'?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+
'/_layouts/15/Reporting.aspx'
+'?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+
'/_layouts/15/expirationconfig.aspx'
+'?ID={ItemId}&List={ListId}'); return false;}}, null); 0x0 0x1 ContentType 0x01 898 Document Set Version History /_layouts/15/images/versions.gif?rev=26 javascript:SP.UI.ModalDialog.ShowPopupDialog('{SiteUrl}'+
'/_layouts/15/DocSetVersions.aspx'
+ '?List={ListId}&ID={ItemId}') 0x0 0x0 ContentType 0x0120D520 330 Send To other location /_layouts/15/images/sendOtherLoc.gif?rev=26 javascript:GoToPage('{SiteUrl}' +
'/_layouts/15/docsetsend.aspx'
+ '?List={ListId}&ID={ItemId}') 0x0 0x0 ContentType 0x0120D520 350
|
