1. Can Shopping be used for non-software requests too?
Yes, Shopping can be used for both software and non-software requests. Using its tight integration with SCCM, Shopping can deploy software automatically to the requestor’s machine in no time. But, it works for other regular services request too – such as on-demand AD group membership request.
Shopping also provides integration scripts that can pass the relevant request information to a third party procurement system, which can be taken up by hardware acquisition team.
2. Does Shopping integrate with other popular service desk tools?
Yes, Shopping has integration scripts that can be used to provide integration with popular service desk tools. 1E has successfully implemented integrations with ServiceNow, BMC Remedy, and HP Service Manager.
3. Does Shopping work with touch devices?
Shopping is compatible with touch devices namely iPad, Surface Pro, and touch monitors. Please note that Shopping works best in its recommended resolution.
4. Can I approve a request when I am not sitting in front of my computer?
Yes, you can. In fact, there are many ways of doing it:
Firstly, as an approver, you don’t even need to be in front of the Shopping web console. When your approval is needed a mail will be sent to you with a link to approve or reject the request.
Alternatively, you can also use Shopping from the touch device of your choice, from a location of your choice.
5. How long does Shopping take to deliver the software?
It’s really quick. If no approval is needed, the software can be deployed to your machine within 5 to 10 minutes.
6. Do I need Shopping specific credentials to log in to website?
Unlike most enterprise systems, Shopping uses your corporate credentials (generally maintained by Active Directory) to grant you access to Shopping website and other components.
7. Can Shopping support multi-forest AD structure? What about different OUs?
Shopping supports dual-forest scenarios using two types of two-way trust: root-level forest trusts and external trusts. The AD forests themselves may be single or multi-domain.
Shopping supports nested OUs, up to 5 levels deep. However, Shopping does not support Groups within OUs.
8. How does Shopping control the visibility of applications by user?
Shopping has very elegant way of handling this. The applications can be classified into logical groupings called categories. Each user is then simply associated with one or more categories to which they then get access to. Shopping can also limit the user visibility based on machine locations too.
9. But then what happens to our role based access control mechanism in SCCM 2012 that we spent months on implementing?
Shopping is fully compliant with the Role Based Access Control in SCCM 2012. This means that shoppers can only access Shopping applications based on their security scope and administrators can only manage devices and shoppers based on their associated SCCM collections.