Organizations leverage SCSM for automation and integration, improving management efficiency and access while planning transitions to Intune.

{"quote":"From an admin point of view, Intune has more features and is easier to manage compared to SCCM.","score":9}

SCSM pricing is complex, with mixed user reviews, enterprise discounts, and potential extra costs for third-party integrations.

{"quote":"SCCM is complex for the admin point of view due to its intricate scalability.","score":"7"}

{"quote":"From an admin point of view, Intune has more features and is easier to manage.","score":"8"}

Users have been utilizing SCSM with varying experience, ranging from one year to a maximum of twenty-five years.

SCSM offers savings and efficiency, but underutilization and reporting issues can limit ROI and lead to potential dissatisfaction.

Many users find SCSM stable, with improvements noted, despite some concerns about cloud transitions and reporting speed.

Microsoft excels in integration; SCCM offers flexible admin; SCSM is stable and reliable, Tableau aids reporting.

We use SCCM for specific tasks due to its remote tool functionality, which Intune lacks. However, Intune is easier for administration. Despite some knowledgeable Microsoft engineers, SCCM's support can be slow. We transitioned from VMware and use Tableau for reporting.

{"quote":"This is one reason we are using SCCM.","score":"8"}

{"quote":"SCCM provides remote tool functionality, which is not in Intune.","score":"9"}

<p>SCSM enhances organizational connectivity and streamlines communication with remote access and efficient notifications. It integrates seamlessly with other Microsoft products and offers scalability and robust reporting, ideal for IT operations management. Known for comprehensive features, it surpasses competitors despite a high price. Users report issues like crashes, requiring better patch management. Though support response is slow, SQL skills are needed for report creation.</p>

They transitioned through various tools before using SCSM. These included in-house solutions, ManageEngine, CA Service Desk Manager, SCCM, SCCPM, BMC Remedy, iTop, Jamf, and ServiceNow. Each offered unique features. Some were more manual, like early tools requiring physical updates. Jamf impressed with custom attributes, while iTop mirrored BMC Remedy. Service Manager faced criticism for its desktop console limitations, lacking a web application. Integration capabilities varied, influencing their current technology choices.

Enterprise users report mixed experiences with SCSM pricing and licensing. Some find it a cost-effective choice compared to market alternatives, while others highlight its expensiveness and complex licensing structure. SCSM requires buying the full System Center suite, with additional charges for add-ons and third-party integrations. The Microsoft licensing model, which factors in infrastructure, cores, and desired support, can be intricate and varies per user scenario. It's sometimes bundled with other Microsoft products, influencing perceived costs.

<p>SCSM surpasses its competitors by offering integrated service management, automation capabilities, and a user-friendly interface, providing efficient support and seamless process optimization for businesses seeking comprehensive IT service management solutions.</p>

<p>The price is high and needs to be cheaper.</p><p>Crashes can occur on client computers, including blue screens, and it lacks mechanisms for checking upgrades or patches before implementation.</p><p>Mobile application integration is needed, and better integration with other services in Azure is required to assist with migration from on-premises to the cloud.</p><p>Patch management is complicated and not user-friendly, affecting the ability to pull reports if systems are not properly patched.</p><p>Lacks comprehensive reporting tools and development requires additional ITSM solutions to achieve necessary functionality, leading to its use as an engine rather than a full-blown product.</p>

Microsoft customer service and support for SCSM show a range of experiences. Some users are satisfied with responsiveness and resolution times, while others find interactions slow or lacking expertise. Larger enterprises often receive better assistance, and severity of issues influences support quality. Many users rely on local vendors for assistance. Some feel self-research is needed due to support limitations. Ratings vary; while some rate the service highly, others see room for improvement.

Implementation of SCSM requires detailed planning and understanding of user roles, services, and SLAs. Various teams either deployed it internally, engaged consultants, or collaborated with partners for deployment. Experience with the platform is crucial, as is having a team of four to five people handling different components. Roles are defined based on the organization's requirements. Collaboration with Microsoft engineers is often pursued for developing workflows.

Some users found SCSM's initial setup straightforward, particularly with training. Others encountered complexity, requiring technical skills and customization. Infrastructure setup was relatively simple but operational aspects like defining SLAs could be challenging and time-consuming. Integration, customization needs, and project scope significantly influenced setup duration. While installations were often completed in days, full deployment varied, requiring additional expertise for specific tasks. Generally, users appreciated the availability of online training materials to aid the setup.

Organizations experience significant value for money with SCSM, noting saved man-hours from reduced travel needs. While SCSM's full potential isn't always leveraged, users find high returns when exploring features like capacity planning and productivity enhancements. Despite these advantages, some consider alternative solutions due to reporting limitations and lack of updates. Generally, when SCSM is utilized more comprehensively, the returns increase, indicating that learning and fully using available features can significantly enhance outcome satisfaction.

Many users of SCSM lean towards the on-premises deployment model, as indicated by its high selection. A smaller group opts for a hybrid cloud model, reflecting a preference for combined approaches. Very few choose the public cloud option. This pattern highlights a strong inclination towards traditional on-premises setups, while cloud-based solutions see limited adoption.

Users advise others considering SCSM to ensure a thorough understanding of the system, focus on user needs, and consider alternatives like ServiceNow if advanced features are desired. They suggest training and simplicity in configuration are crucial. Integration with existing Microsoft environments is beneficial, but limitations exist in non-Windows systems. Some recommend using additional tools like Cireson for improved functionality. User ratings vary, pointing out some improvements are needed, especially in the interface and web portal.

SCSM's customer service and support generally receive a rating of 3 to 4 out of 5.

SCSM suffers from a lack of usability and features in its Self-Service portal and mobile versions. Users find the customization complex, the interface needs improvement, and reporting requires advanced SQL skills. Users struggle with integration, especially with Azure and open-source solutions. The price is high, and system crashes occur during upgrades. Despite some strengths in management, the need for better technical support and simplified deployment remains a concern.

<p>SCSM enhances organizational connectivity and streamlines communication.</p>
<p>It integrates easily with other Microsoft products, providing a seamless experience.</p>
<p>SCSM includes comprehensive features such as helpdesk ticketing, incident reporting, and a robust analysis service.</p>
<p>It offers a cost-effective solution with good scalability and straightforward setup procedures.</p>
<p>SCSM supports comprehensive IT operations management, including incident and service request handling, problem management, and change request tracking.</p>

SCSM is considered stable by many, with users noting substantial improvements over the years. Some appreciate its consistency without significant glitches, while others have encountered minor issues like workflow hiccups. Stability is rated between eight and ten by users, though some express concerns about Microsoft's potential strategic shifts towards cloud solutions. Generally, the experience is positive, despite a few unresolved bugs. Users highlight its performance as satisfactory for on-premises setups, although compliance limitations exist.

SCSM offers distinct integration and ticketing systems, streamlining processes with tools like virtual machine management and active directories. Users appreciate reporting services, security updates, and ease of use. Management modules for incidents and changes enhance operational efficiency while push email updates and patches increase functionality. The digital interface, remote access, and scalability are notable. SCSM integrates seamlessly with Microsoft products, providing auto-orchestration capabilities. It caters to incident, change, and service request handling efficiently.

Primary use cases for SCSM include administrative tasks such as ITSM services, incident and change management, system deployment, and reporting. Organizations utilize SCSM for managing customer service, logging calls, ticketing, and HR onboarding. It supports internal IT operations, cloud integration, and co-management with Intune. Users deploy SCSM for service requests, patch management, and troubleshooting. Many businesses implement it for server updates, security improvements, and to enhance IT efficiency.

SCSM has been used anywhere from about one year to over twenty-five years.

SCSM is scalable, with users praising its ease of deployment and ability to handle diverse company sizes. While some note performance issues with a high number of console connections, others highlight its suitability for large environments. Customization and expansion are possible, supported by third-party add-ons. There are concerns about reporting limitations, yet many find it effective with sufficient licensing. Intune integration adds scalability, appealing to organizations with different roles.

Users evaluated solutions like ServiceNow, BMC Helix ITSM, InfraStruXure Central, Ivanti, and IBM BigFix alongside SCSM. They noted Microsoft's seamless integration compared to third-party tools requiring customization. While both IBM BigFix and Ivanti offer features, SCSM's GUI is seen as more adaptable for administration. Stability and reliability are reasons some chose SCSM over other tools. Tableau is also cited for report integration.

Many automated processes with SCSM improve time management, organize user demands, streamline operations, and enhance communication. It integrates well with Microsoft infrastructure and replaces cumbersome client visits with easier management. Some functionality surpasses Intune, but reporting remains insufficient for project transparency.

Postman gained popularity for its accessibility and usability, surpassing mixed tools previously used for testing and automation.

Organizations use in-house teams for Postman setup and maintenance, relying on internal resources for deployment and updates efficiently.

Most users deploy Postman on-premises, followed by public cloud, with private, and hybrid cloud being less common choices.

Most Postman users prefer AWS for cloud needs, followed by Microsoft Azure, with some using alternate cloud options.

Postman's comprehensive documentation and community forums largely negate support needs, though some users experience varied support interactions and resolutions.

{"quote":"Something that could be better is the inclusion of another type of test, for example, end-to-end tests.","quality_score":"6","sentiment_score":"3"}

Postman's setup is quick and easy, but configuring REST APIs can be complex; JavaScript knowledge may help.

{"quote":"I recommend Postman for all business types.","quality_score":"9","sentiment_score":"10"}

Organizations use Postman for API testing, validation, simulation, documentation sharing, and automated test scripts across teams.

Postman excels in scaling for API testing, but may require additional tools for non-API tasks and can be resource-intensive.

{"quote":"The price is low, making it a reasonable price for the product.","quality_score":"5","sentiment_score":"7"}

7.5

Postman is favored for its ease of use, automation, integrations, and API testing capabilities across different environments.

6.75

Postman needs improvements in automation, integration, interface, documentation, pricing, and advanced testing features for enhanced user experience.

Users recommend Postman for its user-friendly API testing, versatile usage, easy integration, and comprehensive features despite pricing concerns.

Many users have utilized Postman for between one and five years, indicating its sustained value and popularity.

{"quote":"I have not experienced any issues or downtimes.","score":"9"}

{"quote":"Postman is pretty stable.","score":"8"}

Postman offers versatile pricing with free and licensed versions; users find it competitively priced for added collaboration features.

Postman is stable and reliable, with occasional minor issues, generally praised for performance and receiving high stability ratings.

Postman streamlines API testing and development, enhancing efficiency, collaboration, and integration, while facilitating error detection and automation.

Users favored Postman for its ease of use and integration, though Katalon Studio and Selenium met comprehensive testing needs.

{"quote":"The price is low, making it a reasonable price for the product.","score":"8"}

{"quote":"I can use multiple environments, which allows me to create environment variables for each endpoint.","score":"7"}

{"quote":"In Postman, we have collections that contain multiple endpoints that I can test.","score":"8"}

{"quote":"It would be beneficial to expand functionality with additional testing options.","score":"7"}

{"quote":"Something that could be better is the inclusion of another type of test, for example, end-to-end tests.","score":"8"}

<p>Postman is user-friendly and typically learned within minutes. It offers automation and performance testing tools, improving efficiency by over 30%. Users value the Collections feature for organizing API requests and seamless collaboration. It supports REST API testing with ease but has limitations in transaction time visibility, advanced automation, and SOAP API support. Compatibility issues exist, requiring Newman for complete reporting. Improved performance testing options and error logs are needed.</p>

I use Postman to test REST APIs, working with Node.js to ensure endpoints function correctly. Valuable features include collections and environment variables. It could improve by adding end-to-end tests. Currently, Postman leads in the market for API testing.

Several users transitioned to Postman from various tools including SoapUI, LoadRunner, ADAPT Test, and JMeter, citing improved usability and popularity. While ADAPT Test and SoapUI had limitations, LoadRunner and JMeter served different purposes, focusing on performance and load testing. Some preferred Postman for its manual testing and functional capabilities over automation-heavy tools like ReadyAPI. There were also mentions of using Swagger, Selenium, and Python scripting alongside Postman.

<p>Postman lacks support for SOAP API testing and requires more flexibility in this area.</p><p>Transaction times are not visible in Postman, making monitoring difficult.</p><p>Performance testing options are limited, and Postman needs to improve in this area.</p><p>There are challenges with integration, particularly with CRM solutions and test management tools.</p><p>Postman documentation could be improved to better support users.</p>

Postman surpasses its competitors by offering an intuitive interface, automated testing capabilities, and seamless API collaboration, which enhance development efficiency and streamline team workflows. Its community support and extensive integrations contribute to its widespread popularity among developers.

Enterprise Postman users often start with the free or open-source version but may transition to paid plans as needs grow. Licensing options include per-user fees, with moderate and competitive prices relative to other solutions. Companies frequently use its free version; however, for enhanced features and organizational use, a subscription is required. Users acknowledge that licensing costs are in the mid-range, suitable for various business sizes from freelancers to large enterprises.

Several companies successfully handled Postman implementation internally without external assistance. They often utilized small teams, typically involving only two engineers, one senior and one junior. Many reported implementing Proposeman within their organizations without the need for assistance from third-party teams. Continuous updates from Postman eliminated maintenance requirements. Deployments were frequently completed by single individuals, indicating ease of implementation. Multiple personnel and departments managed implementation independently, writing necessary processes themselves.

Customers rarely use Postman support due to its excellent documentation and robust online community. Users can troubleshoot independently or seek help through forums and online resources. While some find the support team responsive and knowledgeable, others note delayed responses and suggest improvements. The availability of online support and ease of problem resolution without direct contact with technical support is frequently mentioned. Support ratings vary, reflecting diverse experiences with Postman customer service.

Among preferences for cloud providers when using Postman, Amazon Web Services is mentioned most frequently. Microsoft Azure is supported by some, while several others opt for different providers. Majority see AWS as a reliable choice. Azure offers certain advantages appreciated by some users. A noticeable portion chooses options outside AWS and Azure, reflecting diverse requirements and priorities.

Postman's initial setup is straightforward, taking a few minutes to a few hours, with most praising its simplicity and ease. Many highlight its quick installation, requiring minimal technical expertise, although complexity may vary depending on specific deployment needs. Users appreciate the lightweight nature of the application and its ability to run as a browser extension or desktop version. Configuration, especially with proxies and APIs, is generally manageable, though adjustments might be necessary for some environments.

Postman customer service and support is rated 8 to 9 out of 10, indicating mostly positive experiences with occasional neutral feedback.

Users predominantly implement Postman within on-premises environments. Many entities utilize traditional on-premises setups for deploying Postman, with fewer opting for cloud-based alternatives. Public cloud solutions account for a smaller segment, while several others choose private cloud. A minority adopt a hybrid cloud approach.

Users advise others to prioritize Postman for its simplicity and efficiency in API testing and integration. It is highly recommended for both beginners and experienced developers. It offers ease of use, a friendly interface, and valuable features for automating processes. Despite some pricing concerns, its versatility and stability are praised. Users suggest enhancing integration with test management tools and organizing collections effectively while considering collaboration and management of secure APIs carefully.

Postman exhibits strong stability, with users noting minimal crashes or issues. The platform efficiently handles daily operations, even under heavy usage by sizable teams. Minor performance hiccups such as latency or slow loading have been noted, but improvements continue. While some reported crashes related to large APIs, the majority find Postman reliable, easy to use, and effective for testing and development needs. The web app version has shown more stability than the desktop application.

Postman users express a need for better user interface and documentation. Users report challenges with automation and integrations, especially with Jenkins and DevOps. They desire enhanced SOAP API testing, multi-window functionality, and database connectivity. Pricing adjustments and environment compatibility improvements are requested. Users also mention the absence of detailed error logs, faster reporting, and end-to-end testing options, along with a more interactive console and support for additional programming languages.

Postman's valuable features include ease of use and a user-friendly interface. Collections and workspaces enable efficient sharing and management. Automation and performance testing are enhanced with data-driven capabilities and validation. It supports multiple environment setups and authorizations while integrating with Newman for strong reporting. Postman handles different API methods, provides seamless variable management, and supports executing complex test suites. Users appreciate its lightweight nature and ability to conduct API testing efficiently without extensive programming skills.

<p>Postman is user-friendly and can be learned quickly, typically within minutes.</p>
<p>It facilitates API testing, allowing users to verify functionality and identify errors efficiently.</p>
<p>Collections feature in Postman is highly valued for organizing and executing grouped requests.</p>
<p>Postman supports automation and performance testing, significantly increasing testing efficiency.</p>
<p>It offers extensive scalability and facilitates easy sharing and collaboration among team members.</p>

Users have been using Postman for a range of six months to eleven years.

Organizations primarily use Postman for API testing, including testing GET and POST requests, validating API responses, and automation. Many teams use it to share collections and test interfaces, integrate with third-party services, and simulate events from other systems. It is used for both manual and automated testing, API documentation, and scheduling everyday runs to check API health. Teams find it user-friendly for API testing and handling complex integration scenarios.

Postman is recognized for its scalability, supporting large user bases and extensive API testing. It allows concurrent operations and integration with Newman. Users report its resource-intensive nature and suggest potential improvements in performance testing features. Even in free versions, it handles multiple instances efficiently, although some report occasional performance issues. It is favored for ease of use in large projects without vertical scaling capability but requires additional tools for comprehensive testing.

Users evaluated alternatives like SoapUI, JMeter, Katalon Studio, Selenium, ReadyAPI, Swagger, Tricentis Tosca, UFT, and others. Postman is often chosen for its ease of use, graphical support, and compatibility with integrations like Jira. Some find Katalon and Selenium preferable for UI and database testing. Others prefer ReadyAPI for its user-friendliness despite higher cost. Comparisons highlight Postman's completeness and open source advantage, frequently leading to its selection.

Postman enhances API testing efficiency by enabling data-driven and automated testing, facilitating error identification, and improving team collaboration. Users experience increased speed and quality, saving time on debugging and code writing. It is user-friendly for non-technical staff and supports both REST and GQL requests. Postman’s features allow easy sharing of test cases, seamless API integration with front-end teams, and improved API documentation visibility, significantly improving API development and monitoring processes.

Organizations preferred Webroot for its speed, resource efficiency, cloud management, and ease of use over other antivirus solutions.

Users deployed Webroot Business Endpoint Protection using internal resources or external help, reporting satisfaction with the implementation process.

{"quote":"I'd rate the solution two out of ten.","quality_score":"4","sentiment_score":"2"}

{"quote":"Webroot Business Endpoint Protection is probably on the cheaper side.","quality_score":"5","sentiment_score":"6"}

{"quote":"Webroot Business Endpoint Protection is very scalable.","quality_score":"5","sentiment_score":"7"}

5.25

{"quote":"It lacks the ability to detect threats effectively.","score":"9"}

{"quote":"The product seems to be stable.","score":"7"}

{"quote":"Webroot Business Endpoint Protection is very scalable.","quality_score":"8","sentiment_score":"7"}

{"quote":"Webroot Business Endpoint Protection needs to improve its ability to detect threats.","quality_score":7,"sentiment_score":2}

1.0

Webroot Business Endpoint Protection is primarily used in Public Cloud, with some users preferring Hybrid, Private Cloud, or On-premises.

7.589086

Webroot Business Endpoint Protection offers quick, easy setup, seamless cloud integration, and straightforward management, despite some initial configuration issues.

Webroot Business Endpoint Protection secures devices and servers, offering antivirus, malware defense, and centralized management for comprehensive security.

Webroot Business Endpoint Protection is praised for its scalability, allowing seamless user expansion and efficient management for growing companies.

Webroot Business Endpoint Protection's customer service is highly rated, but technical support experiences vary, with email preferred over live chat.