We updated our Microsoft SCCM to Version 1806.
Reporting is running, but I cannot see them in SCCM.
Last Saturday, based on the failed Certificate for the Reporting server in SCCM, I can not open up my Reports.
I can go over my SCCM under Reporting and it does shows me 2 Links for the Reporting Server.
I can open those two Links but it shows me on the browser that the Certificates expired, last Saturday, October the 13th.
I can work with those 2 Links in Reporting, but I need to know howto replace that Certificate for the use in SCCM.
Update: I created a new Certificate on my main Microsoft SCCM Server. I updated my IIS for HTTPS with the new Certification for the Config Web Server Certificate and restarted the Service. Now I can see the Reporting in the Configuration Manager Console. But I can't see the Reporting Service on my local installed Configuration Manager Console, anything else in the SCCM Console is working.
Related
I'm trying to connect Visual Studio 2013 to TFS 2013 from a different machine, but it's giving me error:
(TF31002: Unable to connect to this Team Foundation Server).
The Server's IP is working, so the server is online, I've tried things such as turning off Firewall, starting VS as Administrator and it doesn't seem to work.
It's the first time I'm working with TFS, am I missing something?
Thanks in advance.
Try connecting via telnet, e.g telnet yourserver 8080 at the command prompt: this checks if the client has TCP/IP connectivity. Telnet client is not installed by default in Windows, so you may have to turn the corresponding Windows Feature on.
If previous check passes, open the Home page in a browser, e.g. http://yourserver:8080/tfs. If the browser is not configured for Integrated authentication, you will receive a prompt for credential. Insert a valid user and the home page should appear.
Consider which credential you are using: if TFS server is in workgroup, use an account defined on the TFS server; if TFS server is joined to Active Directory, use an account from the same domain. In any case the account must be part of TFS Valid Users group.
I have been using Visual Studio to deploy a Web Service to Azure; downloaded my publish profile to enable that and it was working fine for the past few weeks.
Today I tried to deploy an update and now all my deployments fail with the following:
17:25:03 - Preparing deployment for WindowsAzure1 - 25/03/2013 17:24:53 with Subscription ID 'xxx' using Service Management URL 'https://management.core.windows.net/'...
17:25:03 - Connecting...
17:25:04 - Object reference not set to an instance of an object.
17:25:04 - Deployment failed with a fatal error
I'm not sure what's failing here; is this saying it's unable to connect to the Service Management URL?
Last week I installed an SSL certificate on Azure and now I'm not seeing the option to download my publish settings. I know it used to be there but isn't now. Does having an SSL prevent me from somehow connecting to the management page?
Edit
Before leaving work I removed the certificate but when I then checked for the PublishProfile it was still not showing.
The PublishProfile is not available for any of the other users attached to the subscription - so I don't think it's related to my login.
Edit 2
A bit more drastic; I've now tried deleting my storage and service, to start from scratch. I created a new publishsettings file by removing the subscriptions already imported into Visual Studio and then following the link to "Sign in to download credentials". Next I created a new service and storage in Azure and tried to publish but the deployment still fails when connecting with
Object reference not set to an instance of an object
I have no idea what else I could try or what could be wrong, or where to look to find out.
I got the same error today. Why it wasn't working was because I hadn't uploaded the certificate in the managementportal prior to the publish.
After adding the certificate, everything worked just fine!
You can read more here: http://www.amido.co.uk/mark-omahoney/publishing-in-windows-azure-object-reference-not-set-to-an-instance-of-an-object/
The best way to solve above problem is to download the latest PublishSettings from Azure Management Portal and then use it with Visual Studio. This way your connection to Windows Azure Management Portal from local machine will be verified and validated. Once you have the basic connection working then you can publish your application to specific Windows Azure Service.
Also you can log into your Azure Management Portal and remove all old management certificates which are added in previous publishsettings download attempts.
The problem, in my case, was that my solution Cloud project had the thumbprint of the SSL certificate I'd uploaded in its ServiceDefinition.csdef and ServiceConfiguration.Cloud.cscfg. In my first edit I said that I'd removed the certificate from Azure, but hadn't then removed it from the project files; commenting them out allowed me to publish from Visual Studio again.
I'm not sure why this happened though, I had uploaded the certificate to Azure and was able to connect to my service on https in FireFox so the SSL was "working".
Web Deploy v3.6 BETA3 was released that fixes this issue. To resolve this error, you can download the Web Deploy beta and patch your VS2013 installation. http://azure.microsoft.com/blog/2014/08/11/web-deploy-3-6-beta-released/
Test Validate Connection once you installed the above Web Deploy. If it works, then fine else you can modify the proxy settings used by msbuild.exe (msbuild.exe.config) and check you can now publish from behind a proxy with Web Deploy.
Regards,
Logesh Shan
I think the certificate got corrupt. Deleting the solution .suo file and the .ccproj.user file in my Azure project did it for me.
I have a website that is hosted using IIS7 when deployed, but we are seeing strange behavior with a web service we use that requires a client certificate. So what I'd like to do is debug our website locally to step through the code and take a closer look at the issue.
The problem is that I cannot figure out how to have the website accept client certificates when I'm running it locally (debugging it). If I just run it locally and perform an operation on the website that uses my client cert, it is clearly not pulling it from the browser because I'm getting "m_safeCertContext is an invalid handle" errors.
Is there a way to have the website accept client certificates when running locally? I have IIS7 installed on the same machine that has Visual Studio 2010 Professional installed, and the OS is Windows 7.
Thanks.
SOLVED: Turns out the people not being able to access TFS via VS2010 were using laptops, I didn't put two and two together, and Symantec Endpoint was blocking the ports required.
Some users cannot get to the TFS 2010 server, secured by SSL, from team explorer but can via IE.
For example, I go into VS2010 SP1 and attempt to add a new server, it sits there for a while and then spits out a dialog that basically tells me "Unable to connect to the remote server". If I enter the exact same URL into IE I get access perfectly.
So
https://tfserver:8088/tfs (custom SSL port number) in IE and I get full access
The same detail entered into the add server results in
Any ideas?
Connect to tfspreview through VS2010, you need to install following things :
VS SP1: http://www.microsoft.com/download/en/details.aspx?id=23691
KB2581206: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=39070
Edit: These links are no longer available. The update is now only provided through windows update. See here
KB2662296: http://support.microsoft.com/kb/2662296
I developed a large web application with VS2008 installed on an old Win2k3 server. I now have Visual Studio 2010 installed on Win7 Pro and work on the application fine.
Parts of my web application need to switch into and out of SSL which they did on the Win2k3 server using the IIS tool that creates a private SSL cert.
However I now need to make changes to those parts and now need to be able to test it on the VS2010 internal web server as I no longer have a dev web server like I used to. Is there any way I can do this or is it definitely a no no?
Please take a look here. It is mentioned:
This sample [some sample using HTTPS]
only works when hosted on IIS and
cannot work on Cassini – Visual Studio
Development Server because Cassini
does not support HTTPS.
As this sample is related to .Net Framework 4, I assume that Visual Studio 2010 does not support SSL.
EDIT: The good news is that you can enable SSL for IIS 7.0 (and above). You can find detailed instructions here.
When are done you should be able to access your website over SSL, but browsers will display a warning that says that your certificate is not trusted. However, this can be easily solved in the following way:
1) The common name (CN) for the self-signed certificate that you create for the website should match the computer name that runs IIS and you should access the site using the computer name (https://computerName/ not https://localhost/ or https://IP/)
2) Export the certificate from IIS and import it in the browsers certificate stores. For Internet Explorer the certificate must be added to Windows Certificate Store at Local Computer / Trusted Root Certification Authorities (use Windows Management Console). For other browsers, because they use custom certificate store, the certificate must be imported in their specific location. For example, in case of Firefox to import a certificate go to Tools->Option->Advanced->Encryption->View Certificates->Authorities->Import.
With the release of VS2010SP1 & IIS Express you can now to debug code that uses with https/SSL without having to use a FULL IIS server.