Scrum does not enforce the use of user stories - those are just one type of requirements modeling technique. That aside, if the customer is using the software "as is" with no customization or integration required, the product backlog items will be a mix of infrastructure setup, software installation & configuration, training, and operations transition type work.
One thing to consider is whether the deployment will be a good fit for fixed length iterations. Software development works well with Scrum because most development can easily be divided into sprints of a set duration. Depending on the mix of infrastructure, configuration, testing and rollout, a Lean continuous delivery approach, like Kanban, might be more suitable than iterative delivery (Scrum). Saving Changes...
