Unauthorised Change

[RaymundA]

Hi all,

I raised a Change Request for Windows Server patching for the usual Microsoft patch Tuesday. 

This is a Standard change because we do this patching regularly. This has been approved by management and CAB.

The description and details in the CR describes patching for all Windows Servers in our enviroment.

However, in the midst of patching, there were two server names not added / missed out in the Affected CI tab. We have to manual add each server names in the Affected CI tab.

There was no impact to the users or services. I have added the server names into the Impacted services list. 

This has been flagged as Unauthorized Change? Please advise if it is so.

Thanks very much.

[Dr Atul G- LNG]

HI @RaymundA 

1. The standard changes never go for approval.

2. I am agree it is unauth. change, bcz you are deploying a change on sever which was never in plan , it means no one aware about same. 

[Sohail Khilji · Accepted solution]

Hi @RaymundA ,

If the CI is not part of Affected CI then it will be a unauth change on that particular CI not the whole Change. To speed up the process you can take exception approval on email from CI stakeholder and CAB approvers and needed dignities to add the Additional CI to the change before ''Implement'' or ''scheduled'' state of change.

I hope this helps...

[RaymundA]

What if the change has been implemented on the non-listed CI before the "Implement" and "Scheduled" state?

[Dr Atul G- LNG]

Hi @RaymundA 

I worked in Change domain for good time, the question is mainly on process, you may use this as lesson and try to add the expectation or update the change process.

Practically and by words, if change deployed without approval it will be considered as Unauth , irrespective of State it is.