Yes! Also, come prepared with some questions they may want to ask. It will almost certainly turn into questions you have not anticipated. And if you don't know say so. "Good question. I Don't know, but I'll come back with an answer" It is MUCH better than yes/no when you are BSing. They know it and will start to dig with a knife.
But most importantly, put your self in their shoes as the owner of the company. They want to understand how this makes the company better or worse. How does it make money. How does it impact on the customer (eg automated report is late 24hrs?? If a tree falls and no one hears it...).
And if you have a problem, they can be your best friend. Put it in terms of impact to the company. (eg if you have to much down time, tell them customer can't put in orders. )
You need to realize you are the expert and they are looking for your insight on how to direct the company. Tell them what you need to help do it.
AK
I work for a large enterprise with +100K devices and their naming is standardized on the who made, where it is (ie geographic location) and it's role (server vs desktop). Plus some number to keep it unique. But strangely enough this standard only applies to the unix/linux machines. This standard is of great use because just knowing it's name you know a lot about the environment you are going to support. On the flip side. The Windows machines are the same as the primary user. eg jsmith-1. This has been in place for almost 20years so it works for us.
eg.p = personal
s = server
ott=ottawa
rich=richardson
s=sun micro
h=hp
We would see a names like these
srichh123=server richardson hp 123
AK
"Take that, you hostile sons-of-bitches!" -- James Coburn, in the finale of _The_President's_Analyst_