To check whether Office is installed in a server - ms-office

How do I programmatically find whether MS OFfice is installed in a list of server in a Windows Network.

For XP Office
You have to search in registry:
HKLM\Software\Microsoft\Office\version\Common\InstallRoot

My first thought was 'why would you have Office installed in servers?' but maybe you're using the word server to mean something more general.
The link provided by Svetlozar, above, seems to be for determining if Office is installed locally, not on a list of servers in a Windows network.
Wouldn't it be considered a security risk to allow remote access to this kind of information?

Related

Installing Windows Server for SharePoint

I want to install Microsoft SharePoint 2016 on my computer. To do this, first I need to install Windows Server. And I have 2 questions about doing it in the best way:
1.Which version should I choose - Windows Server 2012 (R2) or 2016?
2.Should I install it directly on computer as a second system OR install it on virtual machine (VirtualBox)
Windows Server 2016. In general the latest Operating System has better security and Microsoft support sunsets at a later date.
Either is fine. Just keep in mind, if you install on a virtual machine, make sure you do not use dynamic memory. SharePoints distributed cache has problems with vms using dynamic memory and Microsoft does not recommend.

Creating a form in SharePoint

I want to build a simple form in SharePoint.
The version of the SharePoint is not important for me, because my form is not going to be used by a real user and its not going to be uploaded to a real server. My windows is a 32-bit win 7.
Someone please help me. Here are my questions:
1- which version of the SharePoint should i install?
2- Is it necessary to install windows server?
3- Should i install Microsoft Office SharePoint Server 2007?
It's worth mentioning that my intention of doing this is to control the process of making the real forms which is going to be done by a company.
You will need windows server for sure and also a 64bit environment. I would suggest to read the basics of MS SharePoint on the Microsoft websites, especially the installation and prerequisites sections...
https://technet.microsoft.com/en-us/library/ee667264.aspx
https://technet.microsoft.com/en-us/library/cc262957.aspx

Installing add-ins for SharePoint Foundation 2010 on Developer Win 7 Pro

I'm having a lot of trouble getting SharePointRS_x64.msi to install sucessfully says it cannot find sharepoint when in fact that sharepoint is installed and running on Win 7 Pro. Because of the operating system I am unable to install the prereq package that comes with SharePoint Foundation 2010 (which includes this reporting addin).
I already have a reporting server set up for my MSSQL2008 instance(win 2008 server R2). It's working when I go to the http:\servername\Reports i'm able to launch the report builder and everything works. I'm now having trouble setting up the other end on SharePoint (different (developement) machine - running win 7 pro).
Any Help would be GREATLY appriciated.
Please let me know if what I want to do is possible.
Thanks,
Mike
I found the solution.
You need to open config file:
C:\Program Files\Microsoft SQL Server\MSRS10.\Reporting Services\ReportServer\rsreportserver.config
In this config find string:
Add Key="SecureConnectionLevel" Value="2"
Change value 2 to 0.
Values meaning:
3 - Most secure-Use SSL for absolutely everything.
2 - Secure-Use SSL for rendering and methods that pass credentials but don't insist on it for all SOAP calls.
1 - Basic Security-Accepts http but rejects any calls that might be involved in the passing of credentials.
0 - Least Secure-Don't use SSL at all.
You have to remember that installing sp2010 on your desktop is going to limit your farm. It is not going to be a fully functional farm. Advanced features like search and user profile sync will not work/get buggy. I guess now, you can add reporting services intergration to the list of things that don't work. Safe your self a lot of trouble but building a vm, which is going to be closer to your production environment anyway.
UPDATE
I thought it might not be supported by Foundation, but it is:
http://msdn.microsoft.com/en-us/library/bb326356.aspx

sharepoint2007 installation

I want to install sharepoint 2007 in my PC. Before installation of sharepoint 2007 server, what are the requirements and after having all the requirements, what are the steps to install in my PC.
Regards,
Abhimanyu
Find the detailed installation guide of SharePoint 2007 on a system here
or you can use SharePoint 2007 VHD (available on microsoft site) and integrate via Virtual PC tool on your machine having XP, Vista OS (not a server OS 2003 or higher).
The first requirement is that you are running an actual Windows Server, not a PC. After that you need to decide if you are going to use a full SQL Server 2005 installation or the free express version. User authentication should also be considered before beginning: will you be using Active Directory, some other directory services or forms based authentication with your own user database?
I suggest you try the MS sites for more details and best practices. This is a good place to start: http://technet.microsoft.com/en-us/library/cc288005%28office.12%29.aspx

Can sharepoint apps be developed in a Visual Studio 2010 stand alone dev box?

Can Sharepoint apps be developed in a Visual Studio 2010 dev box only or does the dev box need to connect to a Sharepoint server? Can the Sharepoint Server be a stand alone machine (no domain controller between the two machines)?
The best practise for SharePoint development is to use a virtual server that contains the SharePoint install itself (and a copy of the portal you're working with), because assuming you are programming directly against the SP API, you will need to be executing your code on the machine that contains the Sharepoint installation itself.
You can program against SharePoint from a non-SharePoint machine through the use of the standard set of SharePoint web services provided, and you can of course create your own services (again sitting on the SP box/VM) to interrogate too. The catch to this approach is that you'll be dealing with return types that are primitive or XML based and you won't have the luxury of SP objects, for example SPUser, SPSite, etc, but for simple query operations at least this is not a bad approach.
IMHO, however, you've far greater flexbility programming against the API itself (Microsoft.Sharepoint.dll) so I'd advise you to get a VM going with all the necessary installs. Yes, it's a pain and time-consuming to set up, but well worth it.
As for Stand-alone options: SharePoint 2007 is not supported on anything non-server in terms of OS, so you'll need something like Server 2008 in order for it to work. SharePoint 2010, however, whilst claiming to only work on Server 2008, can actually work on Windows 7 (Pro and above) with a few hacks. You also have the benefit of 'sandbox' feature deployment in 2010, where you don't in 2007, meaning dev work is more cleanly isolated and less of a risk to a farm as a whole.
Good luck!
You can develop for SharePoint 2010 using VS 2010 using a stand alone setup - this is supported by Microsoft and very much recomended. Infact most of the tools built into VS2010 that will make your life significantly easier will only work with a local copy of SharePoint 2010.
MSDN - Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7...
Yes, if you have Windows 7 or Vista (you need WAS - Windows Activation Services). We have tried it but found that it was better to develop on a Windows 2008 with your own AD.
It will depend on what you are developing, for webparts you will not notice the difference. You will notice the difference when working on the security part og the app.
Sahil Maliks book has a whole chapter on the different options.
you can do sharepoint development by copying certain dlls to your local enviroment but to my understanding this is unsupported and the recommended practice is to use a virtual machine or development on the machine in which the service resides.

Resources