@remote registration

[nodle]

Is anybody else experiencing problems registering @remote via SP-5816-202. I found that it is easier via web image monitor, but sometimes the customer doesn't want us to use their computers.
I've only got about 3 machines that Ive been able to register successfully via SP mode.

[msaeger]

Haven't had a problem but I have only done it with WIM I didn't even know you could do it another way. I haven't had a customer say I can't use their pc to do it but I don't really give them a choice I tell them I need to use their pc to do this.

[unisys12]

I've never done one through SP's either, but... I don't see why it should fail if all the info is put in the proper places. I have had this problem, through WIM and found that I wrote the registration number down wrong or entered it wrong.

If the client gives me the hint that they don't want me on any of their PC's, I just bust out the laptop and hub (same hub I use for packet captures) and walla! If that's an issue, then I just give it up and let it go.

If someone doesn't know how to enter the @Remote info through SP's - go to the @Remote section of TSC and download the "Installing Embedded @Remote" PDF. It's about 9 pages, with the first 4 or so showing how the whole system works. The next few have step by step procedures, with pics, on how to install through WIM and the last page is how to install through SP's.

[nashua]

Is anybody else experiencing problems registering @remote via SP-5816-202. I found that it is easier via web image monitor, but sometimes the customer doesn't want us to use their computers.
I've only got about 3 machines that Ive been able to register successfully via SP mode.

You can register using WIM.you mean scanner folder and e - mail id you can through WIM

[zyqwiz]

You can register using WIM.you mean scanner folder and e - mail id you can through WIM

@remote is nothing to do with scanning - it is a remote monitoring system!

[nodle]

I've never done one through SP's either, but... I don't see why it should fail if all the info is put in the proper places. I have had this problem, through WIM and found that I wrote the registration number down wrong or entered it wrong.

If the client gives me the hint that they don't want me on any of their PC's, I just bust out the laptop and hub (same hub I use for packet captures) and walla! If that's an issue, then I just give it up and let it go.

If someone doesn't know how to enter the @Remote info through SP's - go to the @Remote section of TSC and download the "Installing Embedded @Remote" PDF. It's about 9 pages, with the first 4 or so showing how the whole system works. The next few have step by step procedures, with pics, on how to install through WIM and the last page is how to install through SP's.

I like the idea of using the hub. I'll have to give it a try. I'm actually surprised that I hadn't thought of that.
I know this @remote has been around for a while, but my company really hasn't pushed it until just resently. I think it's a good thing, It just seems that a number of people have alot of questions about the security to their network. That's why I've been doing it via SP, that way I don't have to stumble through a expanation of the whole thing. I know as I work with it more I'll have a better undrerstanding and will be able share that info. with those that have questions.

[manna]

remote monitoring

@remote is nothing to do with scanning - it is a remote monitoring system!

What we monitor remotely in ricoh MFP.Can you guide pls new i am.

[unisys12]

I like the idea of using the hub. I'll have to give it a try. I'm actually surprised that I hadn't thought of that.
I know this @remote has been around for a while, but my company really hasn't pushed it until just recently. I think it's a good thing, It just seems that a number of people have a lot of questions about the security to their network. That's why I've been doing it via SP, that way I don't have to stumble through a explanation of the whole thing. I know as I work with it more I'll have a better understanding and will be able share that info. with those that have questions.

Again, by going to the @remote section of TSC you will not only find a security whitepaper relating to the service, but also a authorization sheet. It basically asked the IT admin, with hat in hand, "Can I please have my MFP do this on your network?"

I actually tried to get our sales people to give these to our clients, after agreeing to purchase a MFP. That way, when we show up to install it, there would be no questions or concerns. Better yet, if they didn't want it... noone brought it up again.

Did it work? Hell no...

There really is a ton of great info there. Way better than the course, which was out dated when I took it two years ago. I don't think their ever going to get the remote inventory system going. The last time I talked to one of the @Remote admins about it, they said they were testing it. That was... a year and half, maybe two years ago!

[Rano]

I found that it is easier via web image monitor, but sometimes the customer doesn't want us to use their computers.

Own laptop and crossover cable? Connect direct to Ricoh.

[nodle]

You can not register @remote via crossover cable, because the machine must be hooked up to the network.

[zyqwiz]

Beore you install @remote, you must get the customer to sign a contract saying all the necessary ports will be available and that the machine will not be switched off at the main switch so that the monitorng works. The @remote resource site has a sample form.